Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__ask_pipeworx_grounded

Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx, picks the right tool from 7,556 across 2013 sources, fills arguments, fetches the data, then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_reason:"not_in_source"|"no_tool_match"|"tool_error"|"data_truncated"|"llm_error"} when the data doesn'

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": {
      "question": "What was Apple's fiscal 2023 revenue?"
    },
    "name": "noaa-ncei__ask_pipeworx_grounded"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAlias for question.
askNoAlias for question.
textNoAlias for question.
inputNoAlias for question.
queryNoAlias for question.
promptNoAlias for question.
messageNoAlias for question.
questionYesYour question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.
prefer_toolNoRun this exact tool instead of letting the router choose, use a name from a previous answer's alternatives[]. Arguments are still filled from your question. Unknown names are refused, never guessed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the internal pipeline (router over 7,556 tools across 2013 sources, argument filling, fetch, extract-only-from-result), the exact success payload shape with evidence/confidence/source/fetched_at, and the enumerated refusal_reason values. The weakness is that the text is cut off mid-sentence ('when the data doesn''), leaving the failure path only partially documented, and it says nothing about cost, latency, or how strict the verbatim-quote requirement is in practice.

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

Conciseness4/5

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

Dense and front-loaded: the differentiator and the guarantee appear in the first sentence, then the return contract. Nearly every clause carries information, but the list of tool/source counts and the alias-heavy schema bloat the surface, and the truncated ending leaves an unfinished thought rather than a clean close.

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 complex, annotation-free, no-output-schema tool, the description does well on the success and refusal payloads, which is the critical missing structured information. However, the text is truncated before finishing the failure-mode explanation, and there is no guidance on evidence verification, latency, or how to react to a 'not_in_source' refusal versus retrying with a different question.

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 every parameter including the seven alias fields and prefer_tool. The description adds only the routing/extraction concept and never mentions prefer_tool's override semantics or the alias behavior, so it neither compensates for nor meaningfully enriches the schema. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific framing — 'hallucination-resistant answer mode for high-stakes reads' — that names both the verb (answer/extract) and the resource class, and it explicitly contrasts the routing with the plain sibling: 'Same routing as ask_pipeworx ... then EXTRACTS the answer using ONLY what the tool result contains.' An agent can tell immediately that this is the fidelity-first variant rather than the ordinary router.

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?

'For high-stakes reads' gives a clear selection context against the plain ask_pipeworx alternative, and the described refusal behavior tells the agent what happens when grounding fails. It stops short of explicit exclusions (e.g., 'not for exploratory or broad queries where recall matters more than citation'), so the when-not side is inferred rather than stated.

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.