Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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.7/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-then-extraction pipeline, the strict 'ONLY what the tool result contains' constraint, the exact success payload including evidence and confidence, and five enumerated refusal reasons. It omits cost/latency and whether the underlying fetch is read-only, and the text is cut off mid-sentence at the refusal explanation.

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 opening sentence front-loads the differentiator, and the return-shape sentence is dense but earns its space by enumerating fields and refusal codes. The final clause is truncated ('when the data doesn''), which leaves a dangling thought and slightly undercuts the otherwise tight structure.

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, but the description compensates by spelling out both the success and refusal payloads in full, which is exactly what an agent needs to branch on. The truncation and the absence of any note on latency or source scoping are the remaining gaps for a router-style tool.

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 alias set and prefer_tool are already documented in the schema. The description adds only indirect meaning, describing that arguments are auto-filled from the question and that routing picks a tool, which contextualizes prefer_tool without naming it or explaining override precedence.

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?

The description states a specific mode of operation: a grounded, extraction-only answer path that routes to a tool, fills arguments, fetches data, and quotes evidence verbatim. It distinguishes itself from the plain ask_pipeworx by the 'hallucination-resistant' constraint. It does not, however, differentiate itself from the many per-source ask_pipeworx_grounded siblings, leaving the source-scoping implicit in the namespace.

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?

'For high-stakes reads' gives a usage context, and the refusal semantics imply the tool is appropriate when verifiability matters. But it never states when to prefer this over the non-grounded ask_pipeworx it references, nor when a direct source tool would be better. Usage is implied rather than prescribed.

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.