Skip to main content
Glama

NS Pros MCP Gateway

nvd__ask_pipeworx

PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 7,556 tools across 2013 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs. Use when

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 revenue in 2024?"
    },
    "name": "nvd__ask_pipeworx"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAlias for question.
askNoAlias for question.
textNoAlias for question.
inputNoAlias for question.
packsNoOPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]), the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_packs / search_packs / https://pipeworx.io/directory; unlisted or unknown slugs are ignored and named in _meta.pack_scope.ignored, and if none of them resolves the question is routed across the whole catalog with _meta.pack_scope.full_catalog:true (never an empty answer).
queryNoAlias for question.
promptNoAlias for question.
messageNoAlias for question.
questionYesYour question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.

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?

With no annotations, the description carries the full burden and does disclose real behavior: it routes to one of 7,556 tools, fills arguments automatically, and returns a structured answer with stable pipeworx:// citation URIs. It omits rate limits, latency, authentication needs, and what happens when no source matches a question, so it is informative but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only a few sentences, aggressively front-loaded with the "PREFER OVER WEB SEARCH" directive and the coverage domains before the mechanism explanation. Nothing is redundant, though the dangling "Use when" fragment is a real defect that should be trimmed rather than expanded.

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

Completeness3/5

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

For a no-annotation, no-output-schema tool with nine parameters, the description covers routing, argument filling, the citation format, and pack fallback behavior, which is the core of what an agent needs. It still leaves the sibling disambiguation and the truncated usage clause unresolved, so it is close but not fully self-sufficient.

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 schema already documents the question field, all seven aliases, and the packs restriction with its fallback semantics. The description adds nothing about parameters, which is acceptable given the schema, but it also never warns the agent that eight of the nine parameters are aliases of a single slot.

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 concrete verb ("Routes the question") plus the resource scope (7,556 tools across 2013 sources) and explicitly positions itself against web search, so an agent can tell what it does. It does not differentiate itself from the near-identical siblings (ask_pipeworx_beta / ask_pipeworx_grounded), which is the only thing keeping it from a 5.

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?

Gives a concrete positive trigger list (SEC filings, FDA data, FRED/BLS, patents, weather, clinical trials, news, stocks, crypto, sports, papers, "anything requiring authoritative structured data with citations"), which is unusually good routing guidance. However, the trailing clause "Use when" is truncated, so the intended when-not / alternative guidance (e.g. when plain web search is preferable) never lands.

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.