Skip to main content
Glama

Duffel

by io.github.pipeworx-io

Entity Profile

entity_profile
Read-onlyIdempotent

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when value was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics — vaccines, cell/gene therapies — from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. sources_used / sources_failed say which of these actually returned data for THIS company — an empty section is a real "no data", not a bug. Pass a ticker ("AAPL"), zero-padded CIK ("0000320193"), OR a company name ("Moderna") — names now resolve via SEC EDGAR's company-name match; a private company (no CIK/ticker) returns resolved:false with an explicit notes line, not a bare failure. type accepts "company" or "ticker" interchangeably — both take the same value shapes above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes"company" or "ticker" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
valueYesTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna") — names resolve via SEC EDGAR company-name match.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
    • changedInput schema / properties / value / description
      Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Despite readOnlyHint=true, the description adds substantial behavioral detail beyond annotations: the exact fan-out destinations, the USPTO PatentsView API sunset and soft-fail behavior, the FDA section's expected-empty caveat for small-molecule/generic-only companies, and the meaning of sources_used/sources_failed. It also explains resolved:false behavior for private companies, giving agents a complete operating picture.

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 long but densely informative, and it is front-loaded with the core value proposition and usage rule before enumerating output fields. The return-section breakdown is necessary because there is no output schema. Minor redundancy with the schema's parameter descriptions keeps it from a 5, but every sentence earns its place.

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?

For a complex tool with two required params, no output schema, and many possible sub-sources, the description covers input shapes, accepted value forms, per-section return contents, failure modes, expected-empty sections, deprecated sources, and the private-company behavior. An agent has enough context to invoke it correctly and interpret any result.

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?

Schema description coverage is 100%, and both parameters are well documented with examples in the schema. The description repeats and elaborates on those examples ('AAPL', zero-padded CIK, 'Moderna') but does not add meaningfully new parameter semantics beyond what the schema already provides. Baseline 3 is appropriate.

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 opens with concrete query patterns ('Tell me about X', 'research Acme', 'company profile for Microsoft') and states a specific, differentiating outcome: 'full cross-source profile of a US public company in ONE parallel call.' It names the resource (US public company) and the verbs (profile, brief, research), and the fan-out detail in the return fields further distinguishes it from generic research tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly instructs 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' giving a clear when-to-use rule. It also covers the private-company edge case ('returns resolved:false with an explicit notes line, not a bare failure'), telling agents when the tool partially succeeds and how to interpret 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.5/5.0
Disambiguation2/5

Several tools are near-duplicates or have blurry boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical today, and the six polymarket tools (edges, arbitrage, bet_research, fill_risk, edge_tracker, kalshi_spread) all target opportunity-finding in overlapping ways. Detailed descriptions help, but an agent can easily pick the wrong one.

Naming Consistency3/5

Most names are readable snake_case with clear verbs like ask_, compare_, resolve_, and validate_, but conventions are mixed: noun-style names (entity_profile, recent_alerts, polymarket_edges) sit beside imperative verbs and domain-prefixed families. There is no camelCase or total chaos, so it is inconsistent but navigable.

Tool Count2/5

32 tools is heavy and exceeds the well-scoped zone; the set spans flight search, general data Q&A, prediction markets, memory, subscriptions, and feedback. Many are platform meta-tools that could be consolidated or hidden behind the main ask_pipeworx router.

Completeness2/5

If Duffel is the intended domain, only duffel_flight_search is present—there is no offer detail, booking, order management, or cancellation, so travel workflows dead-end. As a generic Pipeworx data platform the surface is broader, but that only highlights the mismatch with the server name and a missing coherent domain.

Resources