Skip to main content
Glama

Fact check

fact_check
Read-onlyIdempotent

Fact check a claim on the live web: verdict (supported, contradicted, mixed, not_found) with quotes that are whole sentences our code took word for word from the pages it fetched; no quote, no verdict (unverified). The verdict is AI-written; the quotes are exact. $0.01 per call over x402.

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

Input Schema

NameRequiredDescriptionDefault
claimYesthe claim, 10 to 300 characters
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover read-only, open-world, idempotent safety; the description adds substantive behavior the agent could not otherwise know: verdicts are AI-written while quotes are verbatim whole sentences from fetched pages, ungrounded claims yield 'unverified', and each call costs $0.01 via x402. These are exactly the provenance and billing facts needed before calling.

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 dense sentences, front-loaded with the action and verdict vocabulary, then the grounding guarantee, then cost. Every clause carries information, though the parenthetical stacking makes it slightly run-on.

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?

There is no output schema, so the description must describe returns — and it does, naming the verdict field and the quote format precisely, plus the payment path for a paid tool. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so both the claim length bound and the payment payload are already documented in the schema. The description only adds the price point and that payment settles inside the call, which the schema largely already implies — a baseline score 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 ('Fact check a claim on the live web') and enumerates the exact verdict vocabulary (supported, contradicted, mixed, not_found), which distinguishes it from sibling checks like domain_check or sanctions_check that evaluate fixed record types.

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?

The phrase 'on the live web' plus the verdict list makes clear the tool is for open-web claim verification rather than structured registry lookups, and the 'no quote, no verdict (unverified)' rule tells the agent when to expect a non-answer. It stops short of naming an alternative tool or stating exclusions explicitly.

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.