Skip to main content
Glama

Verify claim

verify_claim
Read-onlyIdempotent

Check one factual claim against public Wikipedia sources and return a verdict (supported, contradicted, outdated, mixed or insufficient_evidence), a confidence score, a short reason, the supporting quote and the source URL. Says insufficient_evidence instead of guessing. Price: $1.00 USDC on Base per call via x402; this MCP call returns payment instructions and the paid HTTP route POST /v1/verify_claim returns the verdict. For a multi-source check use deep_verify. Read-only.

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_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYesOne factual sentence to check.
sourcesNoOptional. Up to 10 sources of your own, used as extra evidence next to the public sources and cited with provider and source_type "caller". The response lists what was used in sources_used.
sources_onlyNoOptional. true = judge the claim only against your sources (no public-source lookups). Needs a non-empty sources array.

Output Schema

NameRequiredDescriptionDefault
toolYesTool name.
resultNoPaid result: { mode, claim: { text, verdict, confidence, rationale_short, citations[] }, why, source, receipt }.
statusYespayment_required: pay the HTTP route with x402 to get the result. ok: result is included.
messageYesHuman-readable summary.
paymentNoPayment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / properties / result / properties / claim / properties / next_step / description
      Previous value: -"1.4.8: present only on unsure, low-confidence or unverified high-worthiness claims. A ready-to-send Deep verify request for this claim (optional, paid separately)."New value: +"Present only on unsure or low-confidence claims (check_answer) or unverified high/medium-worthiness factual claims (extract_claims; opinions and predictions skipped; max 3 per response). A ready-to-send request for this claim (optional, paid separately): Quick check ($0.15) from extract_claims, Deep verify from check_answer and quick_check. extract_claims adds alternatives[] with ready-to-send Quick check ($0.15), Deep verify ($0.75) and Verify claim ($1.00) requests."
    • addedOutput schema / properties / result / properties / claim / properties / next_step / properties / alternatives
      Added value: +{
      +  "description": "1.4.9 (extract_claims): every ready-to-send paid check for this claim. POST body to endpoint with an x402 client.",
      +  "items": {
      +    "properties": {
      +      "body": {
      +        "type": "object"
      +      },
      +      "endpoint": {
      +        "format": "uri",
      +        "type": "string"
      +      },
      +      "method": {
      +        "const": "POST",
      +        "type": "string"
      +      },
      +      "price_usd": {
      +        "type": "number"
      +      },
      +      "tool": {
      +        "enum": [
      +          "quick_check",
      +          "deep_verify",
      +          "verify_claim"
      +        ],
      +        "type": "string"
      +      },
      +      "when": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "tool",
      +      "price_usd",
      +      "endpoint",
      +      "method",
      +      "body"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / result / properties / claim / properties / next_step / properties / tool / const
      Removed value: -"deep_verify"
    • addedOutput schema / properties / result / properties / claim / properties / next_step / properties / tool / description
      Added value: +"1.5.0: quick_check from extract_claims; deep_verify from check_answer and quick_check."
    • addedOutput schema / properties / result / properties / claim / properties / next_step / properties / tool / enum
      Added value: +[
      +  "quick_check",
      +  "deep_verify"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / result / properties / claim / properties / next_step
      Added value: +{
      +  "description": "1.4.8: present only on unsure, low-confidence or unverified high-worthiness claims. A ready-to-send Deep verify request for this claim (optional, paid separately).",
      +  "properties": {
      +    "body": {
      +      "properties": {
      +        "claim": {
      +          "properties": {
      +            "text": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "text"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "claim"
      +      ],
      +      "type": "object"
      +    },
      +    "endpoint": {
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "method": {
      +      "const": "POST",
      +      "type": "string"
      +    },
      +    "price_usd": {
      +      "type": "number"
      +    },
      +    "tool": {
      +      "const": "deep_verify",
      +      "type": "string"
      +    },
      +    "why": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "tool",
      +    "why",
      +    "price_usd",
      +    "endpoint",
      +    "method",
      +    "body"
      +  ],
      +  "type": "object"
      +}
  3. Changed4 schema fields changed
    • addedInput schema / properties / sources
      Added value: +{
      +  "description": "Optional. Up to 10 sources of your own, used as extra evidence next to the public sources and cited with provider and source_type \"caller\". The response lists what was used in sources_used.",
      +  "items": {
      +    "additionalProperties": false,
      +    "anyOf": [
      +      {
      +        "required": [
      +          "url"
      +        ]
      +      },
      +      {
      +        "required": [
      +          "text"
      +        ]
      +      }
      +    ],
      +    "description": "One source: {url} for a public https page we fetch, or {text, title?, url?} for text you already have.",
      +    "properties": {
      +      "text": {
      +        "description": "Source text to check the claim against (up to 20,000 characters). When given, no fetch is made.",
      +        "maxLength": 20000,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "title": {
      +        "description": "Optional title shown in citations.",
      +        "maxLength": 200,
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Public https URL. Fetched with a 3.5 s timeout and a 512 KB cap; http, file and other schemes, private / loopback / link-local / metadata addresses, IP-literal hosts, custom ports and URLs with credentials are rejected (HTTP 400, not charged). With text, it is only the citation link.",
      +        "format": "uri",
      +        "maxLength": 2048,
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "maxItems": 10,
      +  "type": "array"
      +}
    • addedInput schema / properties / sources_only
      Added value: +{
      +  "default": false,
      +  "description": "Optional. true = judge the claim only against your sources (no public-source lookups). Needs a non-empty sources array.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / result / properties / claim / properties / citations / description
      Added value: +"Evidence quotes with url, title and source_type (wikipedia, wikidata, news, europepmc, fred, sec_edgar, or caller for your own sources)."
    • addedOutput schema / properties / result / properties / sources_used
      Added value: +{
      +  "description": "Present when you sent sources: one entry per source with index, kind, url, title, status (used, fetch_failed, empty), chars and reason.",
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, but the description adds material context they cannot: a $1.00 USDC x402 price per call, the fact that this MCP call only returns payment instructions while the actual verdict comes from POST /v1/verify_claim, and a no-guessing fallback verdict. These are exactly the operational traits (cost, two-step payment handshake) an agent must know before invoking.

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?

Front-loaded with what the tool does and what it returns, then cost and payment mechanics in the middle, then the alternative. Dense but nearly every clause carries information; the trailing "Read-only." merely repeats the annotation and is the one redundant element.

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 exists, yet the description still usefully previews the verdict enum, confidence, reason, quote and URL. Combined with the pricing and paid-route explanation, an agent has everything needed to decide whether to call and to interpret the payment-instructions response.

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%, including detailed constraints on sources (fetch timeout, size cap, rejected address classes) and sources_only semantics, so the description is not required to compensate. It only restates the singular-claim scope and mentions sources_used in the response, adding little beyond the schema. Baseline 3 is appropriate.

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 one factual claim against public Wikipedia sources) and enumerates the exact verdict set returned, so an agent knows the output shape before calling. It also names the sibling it is not (deep_verify for multi-source), making it distinguishable from check_answer, quick_check and extract_claims by scope.

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?

"Says insufficient_evidence instead of guessing" and "For a multi-source check use deep_verify" give clear usage context and one explicit alternative. It does not distinguish itself from check_answer or quick_check, which appear to be close siblings, so routing guidance is clear but not exhaustive.

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.