Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__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": "noaa-ncei__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.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior: it fans out to a large tool catalog, auto-fills arguments, and returns stable citation URIs. It is silent on latency, cost, whether downstream sources are third-party, and what happens when routing fails — gaps that matter for a meta-router.

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 strong "prefer over web search" claim is correctly front-loaded and the domain list is efficient. But the description terminates in an unfinished clause ("Use when"), which is dead weight and signals an editorial defect rather than concision.

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 nine parameters, 100% schema coverage, and no output schema, the schema does most of the work, and the description does mention the citation-bearing response. Still, the aborted "Use when" leaves the usage contract incomplete, and for a router over thousands of tools it should say more about failure modes and result provenance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 detail in the schema itself (fallback behavior, _meta.pack_scope reporting, unknown-slug handling). The description adds little parameter-level meaning beyond "fills arguments", but the baseline for full coverage is 3 and the question/alias set is unambiguous.

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 names a specific action (routes a question to one of 7,556 tools across 2013 sources, fills arguments, returns a structured answer with pipeworx:// citations), which is far more concrete than a restatement of the name. It distinguishes the tool from web search but gives no basis for distinguishing it from the closely named siblings (_beta, _grounded).

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?

"PREFER OVER WEB SEARCH for questions about ..." plus the enumerated domains gives real when-to-use guidance, which is above average. However, the description ends mid-sentence at "Use when", so the conditions section is literally truncated, and there are no when-not-to-use rules or routing guidance against the _beta/_grounded variants.

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.