Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does meaningful work: it discloses source authority (authoritative sources), a structured fast path with exact percent-delta math for financial claims, and a graded outcome ("approximately_correct" vs. refuted). It still does not describe the response payload, evidence returned, latency, or failure modes.

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 lead is front-loaded with a long quoted phrase list that costs space but does help trigger matching. However, the text is truncated mid-word ("macro sta"), leaving an incomplete clause with no indication of the remainder, which undermines structure.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-annotation, no-output-schema tool, the description covers purpose, triggering conditions, source authority, and grading behavior reasonably well. The main gap is the truncated tail and the absence of any statement about what a verification result contains beyond a grade label.

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 parameters are already documented, including the tolerance override and its 0.5-50 range. The description adds only marginal meaning by explaining that tolerance drives graded outcomes and that tight values (1-2) suit hallucination detection, but that constraint is largely restated from the schema.

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 states a specific verb and resource: natural-language claim verification against authoritative sources, reinforced by concrete trigger phrases ("fact check", "did X really..."). It also distinguishes two verification paths (structured SEC EDGAR + XBRL for company-financial claims vs. general factual claims), though the second half is cut off mid-sentence, so the full scope is not visible.

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 when-to-use rule: "Use whenever the agent needs to check whether something a user said is factually correct", plus a routing distinction between financial and non-financial claims. It does not name alternative tools or state when NOT to use it, and the truncation removes whatever guidance followed the macro/statistics clause.

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.