Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.3/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 disclosure burden, and it does add real substance: authoritative-source grounding, a structured SEC EDGAR + XBRL path with exact percent-delta math, and grading semantics implied by the schema (approximately_correct). But it omits what the result looks like beyond a grade, source coverage limits, latency/rate behavior, and the rest is cut off mid-sentence, so behavior is only partially disclosed.

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

Conciseness2/5

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

The first sentence is a long slash-separated keyword dump rather than prose, and the description ends abruptly mid-word, which is a substantive structural defect for an agent parsing it. The routing information that follows the keyword list is valuable but is never completed, so the text is both padded at the front and missing at the back.

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?

Given no output schema, a truncated description, and a tool whose correctness hinges on which data path is used, the definition is only marginally complete. Wait — the description's routing sentence is cut off before it explains the non-financial path, and it never says what a verification response contains (verdict labels, supporting evidence, sources).

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 both `claim` and `tolerance_pct` are already documented with examples and a range. The description adds no parameter-level meaning beyond the schema — notably it never mentions tolerance behavior or how claim wording implies tolerance, which is the subtle part of this tool. Baseline 3 is appropriate.

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?

States a specific verb and resource: natural-language claim verification against authoritative sources, with concrete trigger phrasings ("fact check", "confirm or refute", "true or false"). It also sketches two verification paths (SEC EDGAR + XBRL fast path vs. other claims), which distinguishes the tool's scope. It does not name or contrast any sibling tool, and the final routing sentence is cut off, so full scope is not conveyed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use whenever the agent needs to check whether something a user said is factually correct" gives clear situational guidance, and the SEC EDGAR fast path vs. "ANY OTHER factual claim" split implies routing. However the sentence defining the alternative path is truncated mid-word ("macro sta"), so the when-not/alternative guidance is incomplete rather than explicit.

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.