Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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

A4/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 substantial work: auth requirement, paid-tier gate for hourly schedules, SMS verified-phone match and 10/day cap, webhook HMAC scheme with one-time secret, auto-disable after 10 consecutive failures, and rejection of unknown param keys. Gaps remain: no statement about duplicate subscriptions, creation rate limits, or how to inspect/remove what was created.

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 key constraint (OAuth requirement, return value) is front-loaded, which is good. However, the enumeration of supported types duplicates the schema and then cuts off mid-sentence after 'patent_grant', leaving an unfinished list that wastes space without completing the thought.

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 3-parameter, nested-schema write tool with no output schema, the description covers return shape, auth, delivery side effects, and failure handling. The truncated type list is compensated by the exhaustive schema, so an agent has nearly everything needed to invoke it correctly.

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% and the schema's `params` description already documents every type-specific filter in greater detail than the description does. The description's type examples largely restate the schema, adding little new meaning beyond the auth prerequisite. 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 specific verb and resource ('Create a proactive monitoring subscription to a live-data event stream') and adds what is returned ('the new subscription id'). The scope is unmistakable against the sibling `*__subscribe` tools, each of which targets a different provider's feed.

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?

Gives a clear prerequisite ('Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions)') and enumerates supported subscription types with example params, which tells the caller when this tool applies. It does not name alternatives or say when not to use it (e.g. listing or cancelling existing 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.