Skip to main content
Glama

Sec Form D

by io.github.pipeworx-io

Subscribe to Alerts

subscribe
Idempotent

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"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Input Schema

TableJSON 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).
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. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate it's a write operation (readOnlyHint=false) and idempotent (idempotentHint=true). The description adds significant context: returns subscription id, always-on feed, optional delivery, SMS cap, webhook signing details. However, it does not clarify idempotency behavior (whether duplicate subscriptions are prevented or return same id). Still, it provides rich behavioral detail beyond the annotations.

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?

The description is a single dense paragraph (~200 words). It front-loads the core purpose but could be more scannable with bullet points. Every sentence adds value; no fluff. The structure is adequate but could be improved for quick parsing.

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?

Given the tool's complexity (multiple types, delivery options, no output schema), the description covers key aspects: types, params, delivery channels, limitations (SMS cap, phone verification, webhook auto-disable). It lacks explicit return value structure (beyond 'returns id') and error cases, but overall it is fairly complete for a subscription creation tool.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so all parameters have descriptions. The description adds extensive examples and details for each type (e.g., sec_8k items codes, polymarket_edge params) and delivery channels (e.g., webhook HMAC signing). This significantly enhances understanding beyond 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?

The description clearly states the action ('Create a proactive monitoring subscription') and the resource ('live-data event stream'). It distinguishes from sibling tools like list_subscriptions (list) and unsubscribe (remove) by focusing on creation. The verb+resource combo is specific and unambiguous.

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?

The description specifies prerequisites (Pipeworx OAuth account), supported types with examples, and delivery channel constraints (10/day SMS cap). It implies when to use (to get alerts) but does not explicitly state when not to use or contrast with alternatives like recent_alerts. The context is clear but lacks exclusion criteria.

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

All Sec Form D toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Many tools have overlapping purposes, e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all route questions to data sources with minor differences. Form D tools and meta-tools (discover_tools, suggest_questions) further blur boundaries, making it hard for an agent to select the right tool.

Naming Consistency4/5

Most tools follow a consistent snake_case verb_noun pattern (e.g., resolve_entity, validate_claim, subscribe). However, there are minor deviations like bet_research and deep_research without clear verbs, and the ask_pipeworx variants use irregular suffixes.

Tool Count2/5

With 39 tools, the server is over-scoped, including many utility and meta-tools (remember, recall, forget, list_subscriptions) that inflate the count beyond the core domain (SEC Form D and data lookups). A more focused set of 10-15 tools would be more coherent.

Completeness4/5

The tool set covers a very broad range of data sources and actions, including SEC filings, prediction markets, entity profiling, and AI visibility. However, the completeness is uneven; for example, there are many Form D tools but few for other SEC forms, and some areas like weather or clinical trials are only accessible via ask_pipeworx.

Resources