Skip to main content
Glama

Tax Regulations

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.

TDQS

A3.8/5.0
Behavior1/5

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

The description states 'Create ... Returns the new subscription id,' implying each call creates a new subscription, which contradicts the annotation idempotentHint=true. This is a critical inconsistency that misleads the agent about idempotency. The rich behavioral detail (auth, delivery caps, verification) is overshadowed by this contradiction.

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 dense single paragraph, but it front-loads the core purpose and then efficiently enumerates types, channels, and constraints. It is long but every sentence adds necessary value; minor improvement would be breaking into bullets.

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 (3 params, nested objects, 5 enum types) and lack of output schema, the description covers essential context: authentication, type-specific params, delivery options, and important limitations. It does not mention error cases or cancellation behavior, but it is sufficiently complete for typical use.

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?

While the schema already has 100% coverage with descriptions, the description adds concrete examples and constraints: e.g., sec_8k items mapping, phone verification requirement, 10/day SMS cap, webhook auto-disable after 10 failures. This goes well beyond the schema's generic property descriptions.

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 tool's action: 'Create a proactive monitoring subscription to a live-data event stream.' It names specific resource types (sec_8k, polymarket_edge, fred_series) and delivery channels, making it distinct from sibling tools like list_subscriptions or unsubscribe.

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?

Provides clear context on prerequisites (OAuth account required, anonymous/BYO cannot persist) and how to consume alerts (via feed, email, SMS). While it doesn't explicitly contrast with alternatives, the usage constraints and delivery options give sufficient guidance for when to use this tool.

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

All Tax Regulations 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.5/5.0
Disambiguation2/5

Many tools overlap in purpose: ask_pipeworx and ask_pipeworx_beta are identical, while ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve as query/entry-point tools. The two tax-specific tools are distinct, but the sheer number of generic data-access tools makes it difficult for an agent to select the right one.

Naming Consistency2/5

Naming is a mix of snake_case (ask_pipeworx, tax_search), camelCase (ask_pipeworx_beta, compare_entities, discover_tools), and inconsistent verb styles (resolve_entity vs entity_profile vs scan_competitor_ai_presence). No clear pattern is discernible.

Tool Count1/5

The server is named 'Tax Regulations' but only 2 of 33 tools are tax-related. The other 31 tools are unrelated Pipeworx data-access, memory, subscription, and Polymarket tools, making the count wildly excessive and mismatched with the apparent purpose.

Completeness3/5

For the tax regulation domain, tax_search and tax_regulation cover keyword discovery and full-text retrieval, which is a functional core. However, the set lacks any other tax-specific operations (e.g., updates, comparisons, planning), and the majority of the tool surface is irrelevant to the stated server purpose, leaving notable gaps for an agent expecting a coherent tax toolset.

Resources