Skip to main content
Glama

Save fact

save_fact

Add a fact to the brand's fact library, or with fact_id edit, confirm or reject one. Set from_user only when the user told you the fact in this conversation; it is then confirmed as theirs. A fact you found yourself, on their site, the web or a draft, is proposed with its source_url and waits for the user to confirm it. The same fact is stored once. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand": "<brand>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "save_fact"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNonumber: a figure with its period. process: what happens, step by step. example: a named customer or case. claim: anything else the brand states.
textNoThe fact as one self-contained sentence a page could quote.
brandYesBrand or study: its ID from list_brands, or its exact name. A partial name is refused.
statusNoWith fact_id: confirm a proposed fact once the user agrees, or reject it.
fact_idNoEdit this fact, from search_facts. Leave out to add one.
segmentNoThe segment ID or name it applies to; leave out for the whole brand. With fact_id, none makes it brand-wide.
from_userNoTrue only when the user told you this fact in this conversation.
source_urlNoWhere you found it. A new fact needs it unless from_user is true.
stale_afterNoYYYY-MM-DD after which to re-check it, for figures and dated claims. With fact_id, none clears it.
source_excerptNoThe words on the source the fact rests on.
idempotency_keyYesA unique key for this intended action. Reuse it with identical arguments when retrying: the write is not made again, and the reply is the first call's resource as saved (replayed: true) with current status; read tools show the resource's current state. Use a new key for another action.

Output Schema

NameRequiredDescriptionDefault
dataYes
generated_atYesRFC 3339 time the response was made.
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / data / properties / resource / properties / contact
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "For a contact fact: the support phone, email, link or domain answers should give for the brand.",
      +  "properties": {
      +    "channel": {
      +      "description": "phone, email, url, or domain.",
      +      "type": "string"
      +    },
      +    "value": {
      +      "description": "Normalised: phones in E.164, emails in lower case, links as host and path, domains as the registrable domain.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "channel",
      +    "value"
      +  ],
      +  "type": [
      +    "null",
      +    "object"
      +  ]
      +}
    • changedOutput schema / properties / data / properties / resource / properties / kind / description
      Previous value: -"number, process, example, or claim."New value: +"number, process, example, claim, or contact."
  2. Added

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the safety profile, but the description adds important behavior beyond them: from_user facts are confirmed as the user's, found facts are proposed and await confirmation, and the same fact is stored once. It also notes the operation is free.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded, efficient, and free of repetition. Each sentence contributes a distinct operational rule or condition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich schema, annotations, and output schema, the description supplies the workflow details an agent needs: when facts are confirmed versus proposed, how source_url and from_user interact, and how fact_id enables editing or moderation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 11 parameters. The description adds useful cross-parameter semantics, especially the relationship between from_user, source_url, confirmation state, and fact_id-based editing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: add a fact to the brand's fact library, or with fact_id edit, confirm, or reject one. It clearly distinguishes the create and edit/confirm/reject modes within one tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit conditions: use from_user only when the user told you the fact in this conversation, and use source_url for facts found on the site, web, or a draft, which then wait for user confirmation. It also points to search_facts as the source of fact_id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources