Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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
Behavior5/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 so unusually well: it discloses the pipeline (route → fill arguments → fetch → extract), the exact success payload including an evidence quote and confidence, and the enumerated refusal_reason values. It also clarifies that the answer is constrained to source content, which is the key behavioral guarantee an agent needs before trusting the output.

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?

Content is front-loaded: the mode and its differentiator come first, then the mechanism, then the return contracts. Almost every clause carries information, but the text terminates mid-sentence ('when the data doesn'') and the catalog counts (7,556 tools / 2013 sources) are decorative rather than decision-relevant.

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 multi-tool orchestration layer with no output schema and no annotations, the description covers what matters: input expectation, routing behavior, success shape, and failure shape with reason codes. Missing pieces are secondary — no latency/cost/rate expectations for a fan-out-over-catalog tool, and the truncated final sentence leaves the refusal conditions partially 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 coverage is 100% and the schema already documents all nine parameters, including the alias fields and prefer_tool's refusal-on-unknown behavior. The description adds no additional parameter meaning beyond noting that arguments are auto-filled from the question and that a tool is picked from a large catalog. Baseline 3 is appropriate when the schema does the parameter work.

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?

States a specific mode: a hallucination-resistant grounded answering tool that routes, fetches, and then extracts an answer using only the tool result. It distinguishes itself from the plain sibling by naming 'ask_pipeworx' as the same router and emphasizing 'EXTRACTS ... using ONLY what the tool result contains', so an agent can tell the two apart. The final sentence is cut off mid-word, which slightly blunts the framing.

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 an explicit selection criterion, and 'Same routing as ask_pipeworx' anchors it to the sibling an agent would otherwise pick. There is no explicit when-not-to-use statement (e.g., speed/cost tradeoff versus the non-grounded variant), so it stops short of full routing guidance.

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.