Paypal

Ask Pipeworx

ask_pipeworx

Read-onlyIdempotent

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,194 tools across 1868 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs. Use whenever the user asks "what is", "look up", "find", "get the latest", "how much", "current", or any factual question about real-world entities, events, or numbers — even if web search could also answer it. Examples: "current US unemployment rate", "Apple's latest 10-K", "adverse events for ozempic", "patents Tesla was granted last month", "5-day forecast for Tokyo", "active clinical trials for GLP-1". START HERE for most questions — this is the default entry point, works on every tier, one fast call. Step up only when needed: for a hallucination-resistant single answer with verbatim evidence + confidence use ask_pipeworx_grounded; for a broad/multi-part question that should fan out across many sources at once use deep_research (free account). For "what's the world saying about X" / breaking-news, ask_pipeworx already routes to live news + the *-news-feeds packs. Optionally pass packs:["slug","slug"] to restrict routing to specific sources ("answer this using THESE packs"); omit it for full-catalog routing.

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": "ask_pipeworx"
  }
}

Input Schema

Name	Required	Description
`q`	No	Alias for question.
`ask`	No	Alias for question.
`text`	No	Alias for question.
`input`	No	Alias for question.
`packs`	No	OPTIONAL. 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).
`query`	No	Alias for question.
`prompt`	No	Alias for question.
`message`	No	Alias for question.
`question`	Yes	Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

addedInput schema / properties / packs

Added value: +{
+  "description": "OPTIONAL. 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).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed3 schema fields changedSep 27, 2026

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Changed6 schema fields changedJun 3, 2026

addedInput schema / properties / input

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / prompt

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Your question or request in natural language"New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."

addedInput schema / properties / text

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Changed1 schema field changedMay 26, 2026

addedInput schema / examples

Added value: +[
+  {
+    "question": "What was Apple's revenue in 2024?"
+  },
+  {
+    "question": "Any recent SEC filings for $NVDA?"
+  },
+  {
+    "question": "Current price of bitcoin"
+  }
+]

First observedApr 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations it discloses real behavior: routing across the full catalog, argument filling, citation-URI output, availability on every tier, and the pack-scope fallback (unknown slugs ignored, surfaced in _meta.pack_scope, full-catalog fallback rather than an empty answer). It stops short of stating latency, rate limits, or cost implications of a call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Front-loaded with the primary directive ('PREFER OVER WEB SEARCH'), then scope, then escalation path, then the optional pack parameter — a logical order. It is long and repeats the 'start here / default entry point' idea in two places, but nearly every sentence carries routing or fallback information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-required-parameter router with no output schema, the definition covers what it does, when to use it versus alternatives, what it returns (structured answer plus stable citation URIs), and the degenerate pack-scope case. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and the schema already documents the alias set and the full pack_scope fallback semantics, so the description adds little there. It does add intent framing for packs ('answer this using THESE packs') and reinforces that omitting packs means full-catalog routing, but that meaning is largely duplicated from the schema.

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 specific verb and resource: it routes a natural-language question to the correct one of 7,194 tools across 1,868 sources and returns a structured answer with pipeworx:// citation URIs. It also explicitly distinguishes itself from ask_pipeworx_grounded and deep_research by naming the conditions that select each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use triggers ('what is', 'look up', 'get the latest', factual questions about real-world entities) plus concrete examples, and names alternatives with the exact conditions that pick them (grounded for hallucination-resistant single answers, deep_research for broad multi-part fan-out). It also preempts the most likely misuse by stating it already covers live news.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Paypal tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.