Skip to main content
Glama

NS Pros MCP Gateway

noirlab-datalab__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": "noirlab-datalab__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/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 much of it: it discloses that answers are restricted to tool-result content, that evidence is a verbatim quote, that routing spans 7,556 tools over 2013 sources, and that failure is an explicit refusal rather than a guess. The final clause is cut off mid-sentence ('when the data doesn't'), leaving one refusal path under-explained, and nothing is said about latency or cost of the routing step.

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?

Front-loaded and dense with no filler, but the response-shape sentence is an overloaded run-on, and the text terminates mid-clause ('when the data doesn't'), so the most important refusal condition is literally incomplete. Structure is good; execution is marred.

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 the description correctly takes on the return contract — answer, evidence, confidence, source, fetched_at, and the refusal enum. That covers what an agent needs to interpret results; only the truncation and the unmentioned prefer_tool parameter keep it from being fully complete.

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%, so the schema already documents question and all its aliases, so the baseline is 3. The description adds conceptual meaning to 'arguments are filled from your question', but it never mentions the prefer_tool override or its 'unknown names are refused, never guessed' behavior, leaving the most consequential parameter to the schema alone.

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'), the concrete pipeline (route → fill args → fetch → extract), and explicitly contrasts with the sibling ask_pipeworx by noting the same routing but constrained extraction. An agent can distinguish it 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?

'For high-stakes reads' gives a clear context for when to select this over the plain routing sibling, and 'Same routing as ask_pipeworx' implies the alternative. There is no explicit when-not or cost/latency tradeoff statement, but the selection signal is strong.

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.