Skip to main content
Glama

Duffel

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

B3/5.0
Behavior1/5

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

The description states that setting 'mark_read:true' flags events as read and affects future calls, indicating a side effect. This contradicts the annotation 'readOnlyHint: true', which asserts no side effects. According to scoring rules, score 1 for 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 well-structured with distinct sentences for purpose, return data, parameters, and additional usage. It is reasonably concise, though the last sentence about the REST endpoint could be considered extra.

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 explains return structure and provides external access method. It covers most usage aspects but omits details on 'unread_only' parameter and how 'read' state is managed. With no output schema, more detail would be beneficial.

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?

All 5 parameters are described in the input schema (100% coverage), so baseline is 3. The description adds examples for 'type' and 'since' and explains 'mark_read', but does not mention 'limit' or 'unread_only'. Value added is marginal.

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 clearly states it pulls fired events from a subscription feed and returns recent alerts. It specifies the resource (subscription feed) and action (pull/return). However, it does not explicitly distinguish from sibling tools like 'recall' or 'recent_changes', which could also retrieve recent data.

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?

The description mentions polling works fine and provides an alternative REST endpoint for scripts/dashboards. It does not, however, give explicit guidance on when to use this tool versus its siblings or when not to use it.

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