Skip to main content
Glama

Ask Pipeworx — Grounded

ask_pipeworx_grounded
Read-onlyIdempotent

Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx, picks the right tool from 7,604 across 2025 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't directly answer. An "llm_error" also carries refusal_cause ("wall" = our time budget ended before any model call was made; "route"|"threw"|"unparseable"|"wall_after_failure" = a model call failed); refusal_reason itself is unchanged. Use whenever an answer will be quoted, cited, or acted on, and the agent must not invent facts (financial verdicts, legal claims, medical lookups, public statements). Costs one extra LLM call vs ask_pipeworx, prefer ask_pipeworx for casual lookups.

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": "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. Changed1 schema field changed
    • changedInput schema / properties / prefer_tool / description
      Previous value: -"Run 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."New value: +"Run 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."
  2. Changed1 schema field changed
    • addedInput schema / properties / prefer_tool
      Added value: +{
      +  "description": "Run 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.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the read-only/idempotent/non-destructive safety profile, and the description adds substantial context beyond them: the full success payload shape, an enumerated set of refusal_reason values, and the refusal_cause sub-semantics for llm_error including the 'wall' time-budget distinction. This tells the agent how failures manifest, which no structured field supplies.

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 core distinction ('hallucination-resistant answer mode') before mechanics and the sibling comparison. Dense and nearly every clause earns its place, though the parenthetical explaining refusal_cause values is heavy for a single sentence and could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by documenting the returned fields, the refusal envelope, and the failure taxonomy. For a router-plus-extractor tool with openWorldHint, the cost model and refusal modes are exactly the gaps an agent needs filled.

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 itself documents the alias set and the prefer_tool override, so the parameter burden is already carried. The description adds routing behavior context ('fills arguments', 'unknown names are refused, never guessed' is in the schema) but never mentions prefer_tool in prose, so it adds only marginal meaning. Baseline 3 is appropriate.

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 verb and resource: it routes a question to the right tool from a named corpus, fetches data, and extracts an answer strictly from the tool result. It explicitly contrasts itself with the sibling ask_pipeworx ('same routing as ask_pipeworx ... costs one extra LLM call'), so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use trigger ('whenever an answer will be quoted, cited, or acted on, and the agent must not invent facts') with concrete domains, plus an explicit when-not ('prefer ask_pipeworx for casual lookups') and the cost tradeoff that motivates the choice. Nothing is left to inference.

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.