Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.9/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 it does substantial work: routing scale (7,556 tools across 2013 sources), argument auto-fill, strict extract-only-from-result policy, and a full enumeration of refusal reasons with their null-answer shape. It omits operational traits such as latency/cost, whether refusals consume quota, and the truncated final clause leaves the failure path incomplete.

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 value proposition, then mechanism, then return/refusal contract — a sensible order with little waste. Held back by a run-on middle sentence and a description that is cut off mid-clause ("when the data doesn'"), leaving the last thought 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?

With no output schema, the description correctly supplies the response contract: success fields (answer, evidence, confidence, source, fetched_at) and the enumerated refusal reasons. For a 9-parameter tool where 7 are aliases, that is sufficient; the only gap is the truncated refusal explanation and no note on which sources this instance covers.

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 routing override are already documented. The description adds only that arguments are filled from your question rather than supplied per-field, which is contextually useful but not parameter-level detail beyond the schema.

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 ("hallucination-resistant answer mode") plus the mechanism: route to the right tool, fill arguments, fetch, then extract only from the returned data. It distinguishes itself from the plain ask_pipeworx path by the grounding/extraction constraint, though the contrasted sibling is not one of the listed grounded variants.

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 context and the contrast with the standard answer mode is implied by "Same routing as ask_pipeworx... then EXTRACTS the answer using ONLY what the tool result contains." It lacks explicit when-not conditions (e.g. exploratory or low-stakes lookups, latency-sensitive calls).

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.