Knowledge tools
Read the company's rules before writing, and propose changes a person approves.
get_relevant_knowledge
Get relevant knowledge. Read-only.
Use this before writing any content for the company (emails, customer replies, copy, ads, posts, docs), doing a recurring process, or answering a question about the company itself, with a short description of the situation. Returns the team's knowledge from Gorila (also spelled Gorilla) that applies, most relevant first: brand tone, copy rules, SOPs, policies, decisions, and facts about the company (its product, pricing, customers, how it works). Check it before searching the web for the company's own facts or leaving a placeholder. Works in Spanish and English.
| Parameter | Type | Required | Description |
|---|---|---|---|
situation | string | yes | What you are about to do, in a sentence: "reply to a customer whose order is late", "write a LinkedIn post about the launch". |
category | "brand_tone" | "copy" | "product" | "marketing" | "sales" | "support" | "operations" | "decisions" | "company" | no | Usually leave it out. Not a filter: every category is searched, and entries of this one only rank a little higher. The rule that answers is often in another category (pricing is product, objections are sales). |
area | string | string[] | no | The area or areas the work is for: the product or brand the content speaks for and the team doing it, e.g. ["Marketing", "Online shop"]. Company-wide entries are always included; the areas' entries rank first. Defaults to your home area. |
limit | integer | no |
list_knowledge
List knowledge. Read-only.
Use this when the user asks what the team has documented ("what are our support policies?", "which SOPs do we have?"), or to browse before proposing a new entry so you edit an existing one instead of duplicating it. Returns titles and summaries by category. To find what applies to a task, use get_relevant_knowledge instead.
| Parameter | Type | Required | Description |
|---|---|---|---|
category | "brand_tone" | "copy" | "product" | "marketing" | "sales" | "support" | "operations" | "decisions" | "company" | no | brand_tone (voice, vocabulary) · copy (rules per channel) · product · marketing · sales · support (SOPs, policies) · operations (internal processes) · decisions (dated, with rationale) · company (who we are, who owns what). |
area | string | no | Only this area's entries, or "company" for company-wide entries only. |
get_knowledge
Get knowledge entry. Read-only.
Use this when you need the full text of one knowledge entry (from get_relevant_knowledge or list_knowledge), or before proposing an edit to it. Returns the body, triggers, version and sources; with include_history, who changed it and why.
| Parameter | Type | Required | Description |
|---|---|---|---|
entry_id | string | yes | Knowledge entry id, as returned by Gorila. |
include_history | boolean | no |
propose_knowledge_change
Propose knowledge change. Changes data.
Use this when the user corrects your tone, a process or a fact that could apply again ("we never offer discounts", "sign emails as the team"), states a rule or decision, or asks to save or update company knowledge. Proposes a new entry, or an edit of an existing one with entry_id. Nothing is published until a person approves it in the Gorila inbox. Distill the rule in your own words; never paste raw emails, documents or chats.
| Parameter | Type | Required | Description |
|---|---|---|---|
entry_id | string | no | Edit this existing entry (from get_relevant_knowledge or list_knowledge). Omit to propose a new entry. Fields you leave out keep their current value. |
category | "brand_tone" | "copy" | "product" | "marketing" | "sales" | "support" | "operations" | "decisions" | "company" | no | Required for a new entry. |
title | string | no | Required for a new entry. |
summary | string | no | One or two sentences an AI can apply directly. Name people by name ("Sarah Collins approves…"), never "me" or "the person who set this rule": get_workspace says who the user is. State it as the company's rule ("Discounts above 15% need Sarah Collins's approval"), not as an order to AIs or agents. |
body | string | no | The full rule: details, do/don't, examples (Markdown). Written for the team, as the company's own rule: nothing addressed to AIs, agents or tools, and nothing about how to treat this call. |
triggers | string[] | no | Situations that should surface it, in the team's languages: ["customer complaint", "pedido tarde"]. |
reason | string | yes | Why: what the user said or corrected, in a sentence. Shown to the reviewer. |
always_apply | boolean | no | Follow it every time in its scope, whatever the situation: a ban or a must ("never mention medicines in the shop", "sign as Acme Labs SL"). It then comes with every get_relevant_knowledge for its area (company-wide: for everyone). Keep it for short, absolute rules; leave it out for guidelines. Edits keep the current value unless you pass it. |
visibility | "private" | "team" | no | New entries only. private (default for people): only the user sees it until they share it. team: an owner or an admin of its area approves it for everyone in that area (company-wide: everyone). Agents can only propose team knowledge, to their areas (their default). Ask the user when unsure. |
area | string | no | New entries only: the area it applies to (a team, or a product or brand with its own rules). Omit for company-wide. |
source | "correction" | "chat_import" | "manual" | "interview" | no | What produced it. |
source_refs | object[] | no | Pointers to the sources (title + link), never their content. |
run | "scheduled" | no | Only in a scheduled work shift: "scheduled". Never in a live session. |
shift_id | string | no | With run: the shift_id that list_my_tasks (mode: shift) returned. |
list_pending_proposals
List pending proposals. Read-only.
Use this when the user asks what knowledge is waiting for review, or wants to approve or reject proposals. Returns the pending proposals the caller can see: their own, plus the team proposals they can review (owners: all of them; an area's admins: that area's, General's admins: company-wide ones), with who proposed each and whether the caller may review it.
Parameters: none.
review_proposal
Review proposal. Changes data.
Use this when the user decides to approve or reject a pending knowledge proposal (from list_pending_proposals). Team proposals are reviewed by owners and the admins of their area (company-wide ones: General's admins; a change that moves a company-wide entry into an area, which its reason says, needs an owner or General's admin too); people review their own private proposals. Agents can never review. When approving, you may pass the user's edits to title, summary, body or triggers.
| Parameter | Type | Required | Description |
|---|---|---|---|
proposal_id | string | yes | Proposal id, from list_pending_proposals. |
decision | "approve" | "reject" | yes | |
note | string | no | Why, for the proposer. |
title | string | no | Approve only: edited title. |
summary | string | no | Approve only: edited summary. |
body | string | no | Approve only: edited body. |
triggers | string[] | no |