Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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 at all, the description carries the full behavioral burden. It does disclose the verification mechanism (structured SEC EDGAR + XBRL fast path, exact percent-delta math) and implies a graded verdict vocabulary ("approximately_correct", "confirm or refute"), which is real added context. But it never states what the response contains, what verdict categories exist, or what happens for claims outside the authoritative-source coverage, so the disclosure is partial.

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 opening is a long run of quoted trigger phrases joined by slashes, which front-loads the trigger list but pushes the actual purpose statement behind noise. The final clause is cut off mid-sentence, so the definition ends incomplete rather than tightly. It is not padded with filler, but the ordering and truncation cost it.

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 annotations and no output schema, the description should explain the shape of a verdict. It gestures at grades ("approximately_correct", "confirm or refute") but never enumerates them, and the sentence that would have defined non-financial-claim handling is truncated. An agent can initiate a call, but cannot predict the result format.

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% and both parameters are documented in the schema with examples, so the baseline is 3. The description's claim-type routing (financial vs other) does add interpretive value for what `claim` should contain, but the tolerance_pct advice about hallucination detection merely restates what the schema already says.

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 names a concrete verb+resource ("natural-language claim verification against authoritative sources") and enumerates the user phrasings that should trigger it ("is it true that", "fact check", "confirm or refute"). It also carves out a scope distinction: company-financial claims route through the SEC EDGAR + XBRL path while other claim types go elsewhere. It does not, however, distinguish this tool from the many source-specific `validate_claim` siblings, and the text trails off mid-word ("macro sta..."), leaving the scope boundary unfinished.

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?

There is explicit when-to-use guidance: "Use whenever the agent needs to check whether something a user said is factually correct," plus the financial-claim routing rule. The tolerance_pct guidance also ties to a decision (set 1-2 for hallucination detection). No when-not-use or alternative-naming beyond the EDGAR carve-out, 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.