Skip to main content
Glama

Data Edmonton

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

B3.4/5.0
Behavior1/5

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

The description contradicts the annotation idempotentHint: true. It states 'Returns the new subscription id,' implying each call creates a fresh subscription, while the annotation declares the operation idempotent (safe to retry with the same effect). This is a direct contradiction, warranting a score of 1. Other behavioral details (auth requirement, delivery constraints) are present but do not offset the critical inconsistency.

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 dense but well-organized: it opens with a clear purpose, then details supported types, and ends with delivery channel specifics. Every sentence contributes valuable information, and it remains readable despite its length. Slight over-specification for a description, but structure is strong.

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

Completeness3/5

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

The description covers numerous aspects (auth, delivery channels, return id, account verification), but the idempotency contradiction leaves a critical behavioral gap. The response structure is only partially specified (subscription id) and although the schema covers webhook_secret, the description itself lacks that detail. Moderate completeness overall.

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?

The input schema has 100% description coverage, thoroughly documenting all parameters, nested types, and examples. The description adds contextual notes (e.g., OAuth requirement, feed alternatives) but does not significantly enhance parameter understanding beyond the schema. Baseline of 3 is appropriate due to high schema coverage.

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 function ('Create a proactive monitoring subscription to a live-data event stream'), specifies supported subscription types with examples, and distinguishes from sibling tools like list_subscriptions and recent_alerts by noting the always-on feed. It uses a specific verb+resource structure and covers the core purpose.

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 provides clear context for when to use the tool, including the OAuth account requirement and the alternative of pulling alerts via recent_alerts or the public feed endpoint. It implicitly warns against anonymous/BYO usage and explains the conditionality of phone verification, though it doesn't explicitly enumerate when-not-to-use scenarios.

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

All Data Edmonton 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.8/5.0
Disambiguation2/5

Several tool clusters have significantly overlapping scopes. ask_pipeworx and ask_pipeworx_beta are currently identical, and ask_pipeworx_grounded, deep_research, and validate_claim all return grounded answers with different levels of verification. The Polymarket family (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk) also has fuzzy boundaries that could cause misselection.

Naming Consistency4/5

The vast majority of tools follow a verb_noun snake_case pattern (ask_pipeworx, compare_entities, scan_dependency). A few nouns like entity_profile and recent_alerts deviate slightly, and the memory trio (remember, recall, forget) are single-word verbs, but the overall style is consistent and readable.

Tool Count2/5

34 tools is excessive for a server whose name suggests a focused Edmonton open-data scope; only 3 tools actually relate to Edmonton data. Even as a general data platform, the count exceeds the 25-tool threshold and includes many meta-tools (discover_tools, suggest_questions, pipeworx_feedback) that could be consolidated.

Completeness4/5

For the Edmonton open-data subset, search, query, and recent-records cover the core lifecycle well. The broader Pipeworx toolset is comprehensive (entity profiles, comparisons, claims, subscriptions, memory), with only minor gaps like a direct catalog-browsing tool for the 1393 sources.

Resources