Skip to main content
Glama

NS Pros MCP Gateway

noirlab-datalab__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": "noirlab-datalab__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

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully explains that routing, argument filling, and citation-URI generation happen automatically and that the call is non-trivial fan-out across a large catalog; the schema also documents its pack-scoping fallback. It says nothing about latency, cost, failure modes, or what an ambiguous question produces, which matters for a router of this scale.

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 size is reasonable for a router, and the strongest content, the 'PREFER OVER WEB SEARCH' directive and the data-category list, leads the text. However, the trailing 'Use when' fragment is an obviously truncated sentence that wastes space and signals an incomplete definition.

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?

With no annotations and no output schema, the description should explain return shape and edge behavior; it does cover citations but does not cover ambiguity handling or latency at a scale of 7,556 tools. Combined with the cut-off final sentence, an agent has roughly what it needs to call the tool but not a full picture.

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 eight of the nine parameters (the question aliases) are already fully documented in the schema, and packs is exhaustively documented including its ignored-slug fallback. The description adds no parameter meaning beyond that, which matches the baseline 3 when the schema does the heavy lifting.

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 states a specific verb-plus-resource: it routes a natural-language question to one of 7,556 tools across 2,013 sources and returns a structured answer with pipeworx:// citation URIs. That is much more informative than the name alone. It does not, however, distinguish itself from the sibling variants ask_pipeworx_beta and ask_pipeworx_grounded, so an agent cannot tell from this text which of the three to pick.

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?

It gives strong domain-level when-to-use guidance with an explicit 'PREFER OVER WEB SEARCH' directive and a long list of covered data categories listing SEC, FDA, FRED/BLS, weather, stocks, and others. But the sentence 'Use when' is truncated mid-thought, so the promised selection condition never arrives, and the description names no exclusions or sibling alternatives.

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.