Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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.6/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 well: it discloses the auth requirement, the one-time webhook signing secret, HMAC verification formula, auto-disable after 10 consecutive webhook failures, the 10/day SMS cap, the verified-phone constraint, and the paid-tier requirement for hourly schedules. Gaps remain around quota/rate limits on subscribing itself and whether subscriptions expire, which matters for a persistent-resource creation tool.

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 core purpose and auth requirement are front-loaded, which is good. But the description is visibly truncated mid-sentence (it ends at "patent_grant ... , "), so the enumerated type list is incomplete and the text reads as a cut-off fragment rather than a finished definition.

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 persistent-resource creation tool with no output schema, the description does state what is returned (subscription id) and covers the delivery-channel side effects thoroughly. The missing tail of the type list is largely compensated by the schema's complete per-type documentation, but lifecycle information (limits, cancellation, expiry) is still absent.

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 `params` property already enumerates per-type filters in detail, so the schema does the heavy lifting and baseline 3 applies. The description does add marginal meaning beyond the schema — e.g. "items:["5.02"] = officer change" and the note that unknown keys are rejected at subscribe time — but most of its type examples restate the enum and schema text.

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 opens with a specific verb and resource: "Create a proactive monitoring subscription to a live-data event stream," and states the return value (the new subscription id). It does not differentiate this tool from the many sibling `__subscribe` tools or name a companion (list/cancel) tool, so an agent knows what it does but not precisely where it sits in the subscription lifecycle.

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 supplies a real prerequisite ("Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions)") and clarifies that delivery channels are optional additions to the always-on feed. However, there is no when-to-use vs. when-not guidance, no mention of subscription limits or cost, and no pointer to how an agent should manage or cancel a subscription afterward.

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.