Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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

B3.3/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 the internal pipeline (router selection, argument filling, fetch, extraction), the exact success payload, and five enumerated refusal reasons including 'data_truncated' and 'llm_error'. It stops short of latency, cost, or result-size constraints that would explain when truncation triggers.

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?

The mode statement and return shape are front-loaded and dense, but the text is cut off mid-word at 'when the data doesn'', leaving the refusal branch grammatically incomplete. The catalog-size figures (7,556 tools across 2013 sources) communicate scale but are the least actionable content in the block.

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, yet the description fully specifies the success object and every refusal key, so an agent knows what it will get back. Given nine parameters that are almost entirely aliases of one question field, the remaining gap is domain scoping — nothing says what data source this particular 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 coverage is 100% and the schema itself documents all seven aliases for the required question field, so the description is not obliged to repeat them. It adds meaning only for the routing behavior ('fills arguments from your question' and refusal on unknown prefer_tool names), which is already stated in the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the mechanism: it routes to one of 7,556 tools, fetches data, and extracts a verbatim answer with a fixed return shape. However, it never identifies the source domain implied by the 'numverify' prefix, and its thirty-plus siblings share the identical '__ask_pipeworx_grounded' pattern with nearly identical behavior, so nothing in the text helps an agent distinguish this instance from its neighbors.

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' plus an enumerated refusal path implies usage (use when you need quotable evidence, fail loudly rather than guess), but there is no explicit when-not case and no direct comparison to a non-grounded ask_pipeworx variant beyond the passing 'same routing as ask_pipeworx' clause. The agent must infer that the non-grounded sibling is the cheaper choice for low-stakes lookups.

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.