Skip to main content
Glama

Search facts

search_facts
Read-onlyIdempotent

The brand's fact library: what the brand stands behind (confirmed) and facts found on its site, the web or a draft that wait for the brand to confirm them (proposed). With query, the best matches by words and meaning; without, every fact except contact details, proposed first. Quote only confirmed facts as the brand's own and check stale ones with the user first. Add, confirm or reject facts with save_fact.

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>"
    },
    "name": "search_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand or study: its ID from list_brands, or its name (exact or a unique prefix).
limitNoRows per page. Defaults to 25, max 100. A page may hold fewer rows to stay within the response size; follow next_cursor.
queryNoOptional. What to look for, in plain words, for example how long approvals take.
cursorNonext_cursor from the previous page. Leave out for the first page.
statusNoOptional. Defaults to confirmed and proposed.
segmentNoOptional segment ID or name: the brand-wide facts and that segment's own.

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 / facts / items / 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 / facts / items / properties / kind / description
      Previous value: -"number, process, example, or claim."New value: +"number, process, example, claim, or contact."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety is covered. The description still adds real behavioral context: the default result ordering (proposed first), that contact details are excluded from full listings, and the staleness caveat. It doesn't mention response size behavior, though the schema's limit description does.

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

Conciseness4/5

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

Three dense sentences, front-loaded with the resource definition before the query-mode distinction and the mutation routing. Every sentence carries information, though the confirmed/proposed framing plus quoting guidance makes it slightly packed for a scan.

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

Completeness4/5

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

With an output schema present and full annotation coverage, the description only needs to add semantics and routing, which it does. Pagination and status defaults live in the schema, so no critical gap remains for an agent to call it correctly.

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 coverage is 100%, so the baseline is 3, but the description adds value by explaining what query actually does (matching on both words and meaning) and what its absence means (browse everything except contact details). It doesn't restate status/segment/cursor semantics, which the schema already handles well.

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?

States the resource precisely (the brand's fact library) and its two-part scope: confirmed facts the brand stands behind versus proposed facts awaiting confirmation. It also distinguishes itself from save_fact, so an agent knows search vs. mutation without opening schemas.

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?

Explicitly covers both modes (with query = ranked matches by words and meaning; without = full listing, proposed first) and routes mutations to save_fact. It adds a usage rule for downstream behavior too: quote only confirmed facts and check stale ones with the user.

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