Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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.8/5.0
Behavior4/5

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

With no annotations, the description must carry the full behavioral burden, and it discloses meaningful internals: automatic routing across 7,556 tools, argument auto-fill, and a structured answer with stable pipeworx:// citation URIs. It omits latency, failure modes, and whether the answer is ever partial, but the core behavior is unusually well explained.

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 lead 'PREFER OVER WEB SEARCH' is well front-loaded and the domain list earns its space, but the description ends mid-sentence with 'Use when', leaving a dangling fragment. A truncated description signals sloppy structure and wastes the most decision-relevant slot.

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?

For a routing tool with no output schema, the description still covers what comes back (structured answer plus citation URIs) and how catalog restriction falls back to full-catalog routing. Only error/no-match behavior and the difference between this tool and its ask_pipeworx_grounded/beta siblings remain unstated.

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 eight alias parameters and the packs parameter are already fully documented in the schema. The description adds nothing parameter-specific, which is acceptable at this coverage level but earns only the baseline.

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?

The description uses a specific verb ('Routes the question') plus a concrete resource ('7,556 tools across 2013 verified sources') and enumerates the data domains it covers (SEC, FDA, FRED/BLS, USPTO, ATTOM, weather, clinical trials, news, stocks, crypto, sports, papers). It clearly distinguishes itself from generic web search, but it does not differentiate itself from near-identical siblings such as ask_pipeworx_beta or ask_pipeworx_grounded.

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?

Strong 'PREFER OVER WEB SEARCH for questions about ...' guidance with an explicit domain list makes the when-to-use condition unmistakable, and the packs parameter documentation covers the scoping alternative. However, the sentence 'Use when' is truncated, so the exclusions and alternative-routing conditions the author intended are absent.

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.