Skip to main content
Glama

Record a documented fact

record_fact

Add a cited provider residency or facility fact to the catalog using a source URL and verbatim quote; verified facts become tier-A anchors and lift matching cards to ANCHORED.

Instructions

Add a provider residency or facility fact to the catalog, citing a source URL and a verbatim quote. This is how the catalog learns: a verified fact becomes a tier-A anchor and lifts the matching card to ANCHORED. Pass publisher + match[] to add a provider that is not in the catalog yet.

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": {
      "provider": "<provider>",
      "kind": "<kind>",
      "source_url": "<source_url>",
      "quote": "<quote>"
    },
    "name": "record_fact"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNofacility: city.
kindYesWhat kind of fact this is.
nameNofacility: site name, e.g. "Colossus".
matchNoNew provider only: model-id regexes.
quoteYesVerbatim excerpt from that page supporting the fact (>=12 chars).
regionNoresidency: region or country name, e.g. "us-east-1" or "CN".
countryNo2-letter ISO country code, if known.
providerYesCatalog key, e.g. "deepseek".
api_hostsNoNew provider only: API hostnames.
publisherNoNew provider only: the model publisher.
source_urlYesURL of the provider page or filing that states this.
verified_atNoISO date you read it (default: today).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclosing the state change: a verified fact becomes a tier-A anchor and lifts the matching card to ANCHORED. It omits duplicate handling, idempotency, auth requirements, and what happens when the quote or URL fails validation, so a mutation tool still has gaps.

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 action and its effect, with no filler. Some domain jargon (tier-A anchor, ANCHORED) is unexplained but functional in context.

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

Completeness3/5

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

For a 12-parameter mutation with no annotations and no output schema, the description should say what it returns (a created fact, an id, an updated card) and how duplicates or conflicting existing facts are handled. The core call path is covered, but the return and failure semantics are left to inference.

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; the description adds meaning beyond it by binding source_url and quote to the verification requirement, and by explaining that publisher plus match[] only apply when adding a provider not yet in the catalog, a relationship the schema lists but does not motivate.

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?

Specific verb and resource: 'Add a provider residency or facility fact to the catalog.' It also states the write effect ('becomes a tier-A anchor and lifts the matching card to ANCHORED'), which distinguishes it from the read-oriented siblings like locate_model or lookup_prefix.

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

Usage Guidelines4/5

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

Gives a clear usage context ('This is how the catalog learns') plus a conditional branch: 'Pass publisher + match[] to add a provider that is not in the catalog yet.' There is no explicit when-not guidance or named alternative for read-only lookups, but the write path is unambiguous.

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