Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.5/5.0
Behavior3/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 it does disclose useful behavior: automatic tool routing, argument filling, and a structured answer with stable pipeworx:// citation URIs. It says nothing about latency or cost of catalog-wide routing, authentication/quota requirements, or what happens on an unroutable question, and the dangling 'Use when' leaves the behavioral guidance incomplete.

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 strongest guidance ('PREFER OVER WEB SEARCH') is correctly front-loaded, but the long mid-sentence domain list could be trimmed and the description terminates mid-clause at 'Use when', leaving a truncated fragment. A dangling conjunction signals an incomplete definition and wastes the reader's attention.

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 natural-language router this covers a lot: what it accepts, what it does internally, and that the return carries citation URIs; the absence of an output schema is partly offset by that return description. However, the truncated 'Use when' clause and the missing distinction from ask_pipeworx_beta / ask_pipeworx_grounded leave an agent guessing when to pick this variant.

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% and the packs parameter is documented in depth in the schema itself (pack scoping, ignored slugs, full-catalog fallback), so the schema does the heavy lifting. The description adds nothing about the question parameter, its aliases, or how packs constrain routing, so the baseline 3 applies.

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 action ('Routes the question to the right one of 7,556 tools across 2013 verified sources, fills arguments, returns the structured answer') plus the resource class it covers, so the agent knows exactly what it gets back. It does not distinguish itself from the immediate siblings ask_pipeworx_beta and ask_pipeworx_grounded, which appear to be the closest alternatives, so it falls short of 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 explicit when-to-use guidance ('PREFER OVER WEB SEARCH') plus a domain enumeration (SEC filings, FDA, FRED/BLS, USPTO, ATTOM, weather, clinical trials, news, stocks, crypto, sports, papers) that an agent can pattern-match directly. It gives no when-not-to-use condition and no routing between the sibling ask_pipeworx_beta/grounded variants, and the intended guidance is cut off at 'Use when'.

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.