Skip to main content
Glama

NS Pros MCP Gateway

numverify__validate_claim

"Is it true that..." / "fact check" / "verify the claim that..." / "did X really..." / "was Y actually..." / "confirm or refute" / "true or false", natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct. Company-financial claims (revenue, net income, cash for public US companies) verify via the structured SEC EDGAR + XBRL fast path with exact percent-delta math; ANY OTHER factual claim (macro sta

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "claim": "Apple's fiscal 2023 revenue was $383 billion"
    },
    "name": "numverify__validate_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYesNatural-language factual claim, e.g., "Apple's FY2024 revenue was $400 billion" or "Microsoft made about $100B in profit last year".
tolerance_pctNoMax percent deviation still graded approximately_correct (0.5-50). Overrides the tolerance implied by the claim wording, set 1-2 for hallucination detection where any material error must be refuted. Default: implied by wording, capped at 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 burden. It does disclose meaningful behavior: authoritative-source grounding, a structured SEC EDGAR + XBRL 'fast path' with 'exact percent-delta math', and a grading vocabulary ('approximately_correct', 'confirm or refute'). It says nothing about rate limits, authentication, conflicting-source behavior, or the shape of the result (no output schema exists to cover that), leaving real gaps for a verification tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text opens with six quoted trigger phrases before ever stating what the tool does, so the purpose is not front-loaded. The quoted keywords are useful for matching but are padded as an opening, and the truncated final clause wastes space that should have described the non-financial source coverage.

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?

For a two-parameter tool with no output schema, the definition covers the core case well but is incomplete where it matters most: the sentence enumerating the non-financial claim scope is truncated, so an agent cannot tell what sources back ordinary factual claims. Nothing explains the return values, which the absence of an output schema makes more costly.

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 both 'claim' and 'tolerance_pct' fully, including the 0.5-50 range and the 1-2 hallucination-detection guidance. The description adds only indirect colour ('approximately_correct', 'exact percent-delta math') and never references the tolerance override, so baseline 3 is right.

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 definition names a specific verb and resource: 'natural-language claim verification against authoritative sources', and it sketches two routing paths (company-financial claims via SEC EDGAR + XBRL, versus 'ANY OTHER factual claim'). However, it never distinguishes this tool from the three dozen identically named '*__validate_claim' siblings, and the description is cut off mid-sentence ('macro sta'), so the boundary of the non-financial path is left dangling.

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?

Usage context is explicit: 'Use whenever the agent needs to check whether something a user said is factually correct', reinforced by concrete trigger phrasings ('fact check', 'did X really...'). There are no exclusions or named alternatives telling the agent when NOT to reach for this versus a provider-specific sibling, so it stops short of a 5.

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.