Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__subscribe

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes, e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings, params:{topic:"fed"}), "fred_series" (new FRED observations, params:{series_id:"UNRATE"}), "patent_grant" (new USPTO grants for an applicant),

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "params": "<params>"
    },
    "name": "ntsb-investigations__subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesSubscription type.
paramsYesType-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}. clinical_trial: {sponsor?:"Pfizer", condition?:"lung cancer", phase?:"PHASE3"} (sponsor or condition required). form_d: {state?:"CA", industry?:"Biotechnology", min_amount?:500000, exemption?:"06B"} (all optional, omit all to watch every new Form D nationwide). news_keyword: {query:"\"semiconductor sanctions\"", lang?:"eng", domains?:["reuters.com"]} (query required). job_post: EITHER {ats:"greenhouse", board_token:"acme"} (exact board) OR {domain:"acme.com"} (auto-detected), plus optional title_query/location_query substrings. tool_diff: {tool:"form5500", args?:{...}, fields:["headcount"], schedule:"daily"}, re-runs that tool on schedule and fires when the named fields change; tool must be read-only and not need a Pipeworx-held platform key; schedule "hourly" needs the paid tier. new_entity: {state:"CO", name_query?:"dental", entity_type?:"limited liability"}, state is required and must be one of FL, NY, CO, OR, CT, TX, PA. tech_change: {domains:["acme.com","example.org"], technologies?:["Shopify","Segment"]}, domains required (1-200), technologies optional (exact names, case-insensitive) to narrow which detected technologies alert. Unknown keys in form_d/news_keyword/job_post/tool_diff/new_entity/tech_change params are rejected at subscribe time.
deliveryNoOptional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event, must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:"https://..."} POSTs each event JSON to your endpoint, HMAC-signed, the response includes delivery.webhook_secret (whsec_...) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of "<X-Pipeworx-Timestamp>.<raw body>". Auto-disabled after 10 consecutive failing runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

With no annotations at all, the description carries the full burden and does so well: it discloses the returned id, the once-only webhook signing secret plus HMAC verification scheme, the 10/day SMS cap, HTTPS-only webhook with private-host rejection, auto-disable after 10 consecutive failures, silent rejection of unknown param keys, and tier requirements for hourly schedules. These are genuine operational facts an agent cannot get from the schema.

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 opening two sentences are well front-loaded, but the type catalogue becomes a dense wall of prose that substantially duplicates the params schema, and the description ends abruptly mid-entry ("new USPTO grants for an applicant), ") — an incomplete sentence that signals a truncated definition rather than a deliberate one.

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

Completeness4/5

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

For a high-complexity tool with 11 subscription types, nested params, and a nested delivery object, the description covers auth, return value, delivery-channel side effects, and failure behavior — enough to call it correctly. The truncation leaves part of the type catalogue only in the schema and there is no output schema, but the key behavioral facts are present.

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 coverage is 100%, so the baseline is 3, but the description adds real interpretive meaning in places: "items:[\"5.02\"] = officer change," tool_diff "re-runs that tool on schedule and fires when the named fields change; tool must be read-only," and tech_change domains being required 1-200. It loses a point because the type list is truncated mid-sentence after patent_grant, leaving clinical_trial, form_d, news_keyword, job_post, tool_diff, new_entity and tech_change explained only by the schema.

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 first sentence states a specific verb and resource: "Create a proactive monitoring subscription to a live-data event stream," plus the return value ("Returns the new subscription id"). That is unambiguous, but it never references the obvious sibling `list_subscriptions` or `recent_alerts`, so routing between create-a-subscription and inspect-existing-subscriptions is left to the agent's inference.

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 one important precondition — "Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions)" — and per-type filter hints that implicitly say when each subscription type applies. However, there is no explicit when-not-to-use guidance, no mention of listing or deleting existing subscriptions, and no statement about limits on the number of subscriptions.

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.