Skip to main content
Glama

Verify an exact claim

verify_office_procedure_quote
Read-onlyIdempotent

Check whether an exact statement appears word for word in the office's approved procedure documents. Use it to confirm a specific sentence, number or rule before relying on it. Returns VERIFIED with the document title and the surrounding quote, or says the statement was not found verbatim. VERIFIED means the whole statement was found together in one document; when the sentences of a long statement are found only in part, or only apart, it says not found and shows the partial match. Case, spacing and curly quotes are ignored, but a paraphrase will not match. Uses no language model.

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": {
      "claim": "<claim>"
    },
    "name": "verify_office_procedure_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYesThe exact statement to look for, copied as closely as possible from the source, for example: Refunds are issued within 14 days.
corpusNoOptional corpus id. Leave it out to use the office's default corpus, which is right for almost every call; a made-up id is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover safety and idempotency; the description adds genuinely new behavior: the whole statement must appear together in one document, partial or split matches return not found with the partial shown, and case, spacing and curly quotes are normalized while paraphrases fail. This is precisely the matching semantics an agent needs and cannot get from structured fields.

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?

Purpose comes first, followed by usage, then return semantics and normalization rules; every sentence contributes. It is dense but not padded, with only mild redundancy between 'exact statement' and 'paraphrase will not match'.

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?

With no output schema, the description carries return-value duty and does so: VERIFIED plus document title and surrounding quote, or a not-found result with the partial match. Combined with the matching rules, nothing an agent needs to interpret results is missing.

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 real meaning to the claim parameter by spelling out the normalization rules and the exactness requirement that go beyond 'copied as closely as possible'. It says nothing about the optional corpus parameter, leaving that to the schema.

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 a specific verb and resource ('check whether an exact statement appears word for word in the office's approved procedure documents') and pins down the exact-match nature, which separates it from the sibling ask/search tools implied by its phrasing. An agent knows this is verbatim lookup, not semantic retrieval.

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?

'Use it to confirm a specific sentence, number or rule before relying on it' gives a clear trigger, and 'a paraphrase will not match' plus 'Uses no language model' implicitly steer rewording queries elsewhere. It never names the sibling search/ask tools or states exclusions explicitly, so it stops short of a 5.

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.