Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and largely meets it: it discloses the pipeline (route → fill args → fetch → extract), the strict grounding constraint, and the complete success and refusal payload shapes with all five refusal_reason values. It omits operational traits such as latency or cost relative to ask_pipeworx, and the final sentence is truncated mid-clause.

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?

Front-loaded with the mode and its distinguishing behavior, then the return contract — a sensible order with little waste. The enumerated return/refusal blocks are justified because no output schema exists, but the trailing sentence is cut off mid-word, leaving an incomplete thought in the definition.

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 router-plus-extractor tool with no output schema, the description covers what matters: what it does, how grounding works, and the exact success and refusal response shapes. Missing only cost/latency expectations and an explicit recommendation of when to fall back to the non-grounded sibling.

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%, including all eight alias parameters and prefer_tool, so the schema already documents each field. The description adds only the general behavior that arguments are auto-filled from the question; it says nothing specific about question wording or how prefer_tool interacts with the router beyond what the schema states.

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?

States a specific mode ('Hallucination-resistant answer mode') with an explicit differentiator from its sibling: same routing as ask_pipeworx, but extraction is constrained to the tool result. The agent can distinguish this from ask_pipeworx and ask_pipeworx_beta without opening any schema.

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 criterion against the plain ask_pipeworx sibling, and the description implies the tradeoff being made. It stops short of explicitly stating when NOT to use it (e.g., casual lookups where the grounded path is slower or costs more), so the routing decision is only partly spelled out.

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.