Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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 the multi-step behavior: it selects a tool, fills arguments, and returns an answer with stable citation URIs. It does not mention latency, cost, auth, or failure modes, and the pack-scope fallback semantics live only in the schema, so transparency is good 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.

Conciseness3/5

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

The critical 'PREFER OVER WEB SEARCH' directive is correctly front-loaded, and the domain list is informative rather than filler. But the description ends mid-sentence on 'Use when', leaving an obvious truncation that wastes the closing slot where the decisive guidance should sit.

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 router over thousands of tools with no output schema, the description does cover the return shape (structured answer plus citation URIs), which is the main thing an agent needs. It stops short on latency, result confidence, and the incomplete 'Use when' clause, so an agent still has open questions before calling.

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 all nine parameters — including the eight question aliases and the packs filter — are already documented in structured data. The description adds nothing about parameter behavior (e.g. that aliases are equivalent, or when to use packs), so the baseline 3 applies.

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 concrete verb and mechanism: it 'routes the question' to one of 7,556 tools across 2013 verified sources, fills arguments, and returns a structured answer with pipeworx:// citation URIs. The enumerated data domains (SEC, FDA, FRED/BLS, USPTO, ATTOM, etc.) make the resource scope unmistakable, and the opening clause distinguishes it from web search.

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?

The first sentence is an explicit routing rule with a named alternative ('PREFER OVER WEB SEARCH') plus the condition that selects this tool (questions needing authoritative structured data with citations). However, the trailing fragment 'Use when' suggests a when-not or prerequisite clause that was cut off, so the guidance is one-sided.

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.