Skip to main content
Glama

search_claims

Search the Signetex register of verified claims (public pages and MCP-only entries) across machine-intelligence, human-impact, politics-economy and corporate-promises. Internal or paywalled corporate entries are not included, nor are the speculative Futures essays. Returns matching entries with canonical URLs. Signetex grades evidence and issues no true/false verdicts.

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": "search_claims"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoRegister area: machine-intelligence (the AI itself), human-impact (AI and humans) politics-economy (forecasts by governments, central banks, politicians and economists) or corporate-promises (company and CEO statements).
kindNoEntry kind: finding, forecast or possibility (also accepts the stored values befund, prognose, moeglichkeit).
gradeNoEvidence grade: E0, E1, E2, E3 or E4.
limitNoMaximum number of results to return (default 10, max 50).
queryNoFree-text search over English and German claim text, speaker, organisation, topic and ID. Optional if filters are set.
outcomeNoForecast outcome: open, met, partial, not_met, unclear (German stored values also accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / area / description
      Previous value: -"Register area: machine-intelligence (the AI itself), human-impact (AI and humans) or politics-economy (forecasts by governments, central banks, politicians and economists)."New value: +"Register area: machine-intelligence (the AI itself), human-impact (AI and humans) politics-economy (forecasts by governments, central banks, politicians and economists) or corporate-promises (company and CEO statements)."
    • changedInput schema / properties / area / enum
      Previous value: -[
      -  "machine-intelligence",
      -  "human-impact",
      -  "politics-economy"
      -]New value: +[
      +  "machine-intelligence",
      +  "human-impact",
      +  "politics-economy",
      +  "corporate-promises"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / area / description
      Previous value: -"Register area: machine-intelligence (the AI itself) or human-impact (AI and humans)."New value: +"Register area: machine-intelligence (the AI itself), human-impact (AI and humans) or politics-economy (forecasts by governments, central banks, politicians and economists)."
    • changedInput schema / properties / area / enum
      Previous value: -[
      -  "machine-intelligence",
      -  "human-impact"
      -]New value: +[
      +  "machine-intelligence",
      +  "human-impact",
      +  "politics-economy"
      +]
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses what is included/excluded and that results carry canonical URLs, and clarifies that Signetex issues no true/false verdicts. It does not describe pagination/default behavior, result ordering, or safety/read-only characteristics beyond what 'search' implies.

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 sentences, front-loaded with the core action and scope. The exclusions and grading caveat earn their place by preventing misuse, though the prose is somewhat dense.

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?

The tool has six optional parameters and no output schema, so the description should help an agent understand results. It explains inclusion/exclusion and canonical URLs but does not describe the fields returned for matching entries, result ordering, or edge cases like empty results. It is adequate but not fully complete.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all six parameters and enum values in detail. The description adds no parameter-level semantics beyond naming the register areas, so baseline 3 is appropriate.

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 gives a specific verb+resource: searching the Signetex register of verified claims, with explicit topic areas and exclusions. It is clearly distinguishable from a bare lookup, but it does not explicitly differentiate from siblings such as get_entry or compare_forecasts.

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 inclusion/exclusion boundaries (public pages and MCP-only entries, excluding internal/paywalled corporate entries and Futures essays), which implies when to use it. However, it gives no explicit routing guidance for alternatives like get_entry or due_forecasts, nor does it say when not to use search.

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