Skip to main content
Glama

NS Pros MCP Gateway

noaa-ndbc__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-ndbc__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

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 burden and does substantial work: it discloses the routing scale, that arguments are auto-filled, that answers are constrained to verbatim tool output, and it enumerates the success payload fields and the refusal_reason values (not_in_source, no_tool_match, tool_error, data_truncated, llm_error). What is missing is operational context such as latency, cost, or what happens when prefer_tool targets an unresolvable tool, and the text is cut off mid-sentence at the final refusal case.

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 well front-loaded and dense with signal, but the text is truncated mid-sentence ('when the data doesn't'), leaving the last and arguably most important refusal condition unfinished. The 'picks the right tool from 7,556 across 2013 sources' clause adds color but consumes space that the cut-off sentence needed.

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 tool with a complex router plus extraction pipeline, the description covers the return contract (answer, evidence, confidence, source, fetched_at) and the failure modes, which is exactly what an agent needs given there is no output schema. It falls short only because the final clause is truncated and the relationship between prefer_tool and the router is left unstated.

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 all nine parameters including question and its aliases and prefer_tool. The description adds only indirect meaning — that arguments are filled from the question and that routing happens automatically — without explaining prefer_tool, its alternatives[] source, or alias behavior. 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 states a specific verb chain and resource: it routes a natural-language question to one of 7,556 tools, fills arguments, fetches data, and extracts an answer strictly from the tool result. It also explicitly distinguishes itself from the sibling ask_pipeworx by contrast ('Same routing as ask_pipeworx' but 'hallucination-resistant' / extraction-only), so an agent can tell the two apart without opening either schema.

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?

The phrase 'for high-stakes reads' implies the usage context and implicitly routes lower-stakes questions to ask_pipeworx, but no explicit when-not condition or side-by-side alternative guidance is given. The agent must infer the tradeoff (e.g., stricter refusals, higher cost/latency) rather than being told.

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.