Skip to main content
Glama

Read a claim and its exact evidence

get_claim
Read-only

Fetch a claim's origin, type, evidence spans, and review status, plus exact-span checks confirming where a quotation occurs in the saved source.

Instructions

Read a claim with its origin, type, evidence spans and review status.

Exact-span checks confirm where a quotation occurs in the saved source.

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_id": "<claim_id>"
    },
    "name": "get_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claim_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real context by disclosing that evidence is returned as exact spans verified against the saved source. It stops short of saying what happens for an unknown or stale claim_id.

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?

Two short sentences, front-loaded with what you get back; no filler. The second sentence is somewhat detached ('Exact-span checks confirm where a quotation occurs in the saved source') but carries genuine information.

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?

An output schema exists, so return-value documentation is not required, and the read-only, single-parameter shape is simple. The remaining gap is the provenance of claim_id and any failure behavior, which an agent needs in order to invoke this correctly.

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

Parameters2/5

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

The single parameter claim_id has 0% schema description coverage, so the description must compensate and it does not. It never says what form a claim ID takes or where the agent obtains one (presumably from a search or list call), leaving the only required input under-specified.

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

Purpose4/5

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

States a specific verb and resource ('Read a claim') and enumerates the returned facets: origin, type, evidence spans, and review status. That is enough to distinguish it from get_source and search_sources, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when it already has a claim and wants full detail. There is no statement of when not to use it, no mention of how a claim relates to a source, and no explicit routing to get_source or search_sources.

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