Skip to main content
Glama

Duffel

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

A4.7/5.0
Behavior5/5

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

Discloses required OAuth account, delivery channel specifics, SMS cap of 10/day, and webhook auto-disable after 10 consecutive failures. Annotations indicate idempotentHint=true and readOnlyHint=false, and description does not contradict; it adds substantial behavioral context beyond 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?

Well-structured with clear sections for types and delivery, but slightly lengthy. Could be trimmed without losing clarity.

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

Completeness5/5

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

Covers all aspects: creation, types, parameters, delivery channels, limits, and webhook verification. No output schema, but description is sufficient for an agent to use correctly.

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?

Despite 100% schema coverage, the description adds rich examples and constraints for each type (e.g., items codes, topics, series_id), and details delivery channel requirements (verified phone, webhook signing secret).

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?

Description clearly states 'Create a proactive monitoring subscription to a live-data event stream', providing a specific verb and resource. It distinguishes from siblings like list_subscriptions and unsubscribe by focusing on creation.

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?

Explicitly mentions requirement of Pipeworx OAuth account and gives examples for each subscription type with parameters. However, it does not explicitly state when not to use or compare to alternatives.

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

All Duffel 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.6/5.0
Disambiguation3/5

The set is organized into clusters (Pipeworx querying, Polymarket analysis, entity research, subscriptions, memory), but several tools within a cluster have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, deep_research, and validate_claim all answer questions, and polymarket_edges, bet_research, and polymarket_arbitrage all surface trading opportunities. The very detailed descriptions help an agent choose correctly, but the boundaries are not crisp enough for a 4.

Naming Consistency3/5

Most names are lowercase snake_case and there are consistent prefixes like polymarket_ and pipeworx_, which aids predictability. However, the verb/noun ordering is inconsistent across the set (ask_pipeworx, bet_research, entity_profile, duffel_flight_search, ai_visibility_check), and some names are noun-heavy while others are verb-first. It is readable but not a uniform convention.

Tool Count2/5

At 32 tools the surface feels heavy for a coherent server; the rubric treats 25+ as too many. Several tools are wrappers or variants of the same underlying capability (ask_pipeworx_beta, polymarket_edges vs bet_research, ai_visibility_check vs scan_competitor_ai_presence), so the count overstates real functional breadth.

Completeness3/5

The research/data side is very complete: querying, grounded verification, deep research, entity resolution, comparison, profiles, monitoring, memory, and feedback are all covered. However, the Duffel flight tool only searches and never books, so if the server is meant to be a flight agent there is a notable dead end; the broader toolkit also lacks direct CRUD for most resources beyond subscriptions.

Resources