Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does reveal real behavioral traits — the SEC EDGAR/XBRL fast path, "exact percent-delta math," and grading into an approximately_correct verdict — but says nothing about what sources back the general path, latency/cost differences between the two paths, or what the full set of verdict labels is.

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 leading cluster of quoted trigger phrases is front-loaded and useful for routing, but it reads as keyword stuffing rather than prose, and the body terminates mid-sentence. A reader gets the gist but the text is visibly incomplete and unstructured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 explain what a call returns — it only implies a verdict scale via "approximately_correct" and never enumerates the other grades or the evidence returned. Combined with the truncated second routing branch, an agent cannot fully predict the behavior of non-financial claims from this definition.

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%: both `claim` and `tolerance_pct` are already documented in the schema, including the 0.5-50 range and the 1-2 hallucination-detection advice. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 and resource ("natural-language claim verification against authoritative sources") and distinguishes two internal paths: company-financial claims via the SEC EDGAR + XBRL fast path versus all other factual claims. The purpose is unmistakable, but the second branch is cut off mid-word ("macro sta"), so the scope of the general path is never actually stated.

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?

It gives an explicit trigger condition: "Use whenever the agent needs to check whether something a user said is factually correct," backed by a list of user phrasings ("fact check", "did X really..."). It also routes between the structured financial path and the general path, though the routing rule for non-financial claims is truncated before completion and no sibling alternatives are named.

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.