Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__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": "nist-standards__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?

With no annotations at all, the description carries the full burden and does substantial work: it discloses the routing-then-extract pipeline, the verbatim-evidence constraint, the exact success payload shape, and an enumerated set of refusal reasons including tool_error and data_truncated. It omits cost/latency characteristics and what happens when a question is ambiguous rather than absent from source, and the final sentence is cut off 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?

The core differentiator (grounded extraction, refusal rather than fabrication) is front-loaded in the first two sentences, and the payload shapes are stated compactly. Minor deduction for the truncated trailing sentence, which leaves a promised condition unfinished.

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?

There is no output schema, so describing the return payload and refusal contract is essential and the description does it explicitly, including evidence and confidence fields. For a high-stakes grounded-retrieval tool the remaining gap is operational behavior — latency, cost, or behavior on ambiguous questions — not the contract itself.

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% and the schema itself enumerates the seven aliases for 'question' plus the prefer_tool override semantics. The description adds no parameter-level meaning beyond that, so the baseline 3 applies — the schema is doing all the parameter work.

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 names a specific capability — a grounded, extraction-only answer mode — and explicitly frames its relationship to the sibling router ('Same routing as ask_pipeworx'), then states the differentiating behavior: it answers using ONLY what the tool result contains. An agent can distinguish this from ask_pipeworx and ask_pipeworx_beta without opening a 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?

The opening phrase 'for high-stakes reads' gives a clear selection criterion against the ungrounded siblings, and the prefer_tool parameter doc explains the override path. It stops short of explicitly stating when NOT to use it (e.g. exploratory or low-stakes lookups where the plain router is cheaper/faster).

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.