Skip to main content
Glama

Get a PaliAnswers claim

get_claim
Read-onlyIdempotent

Fetch one PaliAnswers claim by its id or slug, for example one listed by list_claims; give exactly one of id or slug. Returns the claim with PIPD's full answers, sources, themes and page URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoClaim id, as returned by the other tools.
slugNoClaim slug: the last part of its page URL, e.g. the slug in /myths/<slug>/.

Output Schema

NameRequiredDescriptionDefault
idYesPaliAnswers claim id.
urlYesThe claim's page on PaliAnswers. Cite and link it.
noteNo
claimYesThe claim or myth, as PIPD phrases it.
matchNosearch_claims only: strong when the score is at least 0.70.
scoreNosearch_claims only: match score, 0 to 1.
themesYes
answersYesPIPD's answers to the claim, in markdown.
sourcesYesPIPD's sources, as markdown citations with links.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds a constraint the structured data lacks: exactly one of the two optional parameters must be supplied, which prevents a no-arg or both-args call. It also sketches the payload (full answers, sources, themes, page URL) even though an output schema exists.

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?

A single tight sentence pair: the operation and identifier constraint come first, the return contents second. No filler, no restatement of the name or title.

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?

Output schema is present, so the brief return summary is a bonus rather than a burden, and the read-only nature is carried by annotations. For a two-parameter fetcher, everything an agent needs to invoke it correctly is stated.

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 per-field meaning of id and slug is already fully documented, establishing a baseline of 3. The description goes beyond that by stating the exclusive-or requirement between the two optional parameters, a semantic rule the schema cannot express.

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?

The description states a specific verb and resource ('Fetch one PaliAnswers claim by its id or slug') and names list_claims as the tool that surfaces the identifiers, which gives the agent a sense of where this fits. It does not contrast with search_claims, so the separation from the other retrieval sibling is left to inference.

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?

It establishes the precondition of having an id or slug ('for example one listed by list_claims') and imposes an invocation constraint ('give exactly one of id or slug'). There is no explicit when-not guidance or routing to search_claims for text-based lookup, so usage is implied rather than spelled out.

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