Skip to main content
Glama

Dtcc Swaps Recent

dtcc_swaps_recent
Read-onlyIdempotent

Most-recently disseminated swap transactions from DTCC's public, CFTC-Part-43-mandated real-time price dissemination feed (pddata.dtcc.com), live. Covers CFTC-regulated swaps (commodity CO, credit CR, equity EQ, FX, interest-rate IR), SEC-regulated security-based swaps (credit CR, equity EQ, interest-rate IR), and Canadian-regulator swaps (credit CR, equity EQ, interest-rate IR). Each record carries notional amount/currency, fixed/floating rate terms, execution/effective/expiration dates, product identifiers, and an actionType (NEWT=new trade, CORR=correction, EROR=error/cancel, MODI=modification, TERM=termination), corrections and cancellations of an earlier trade appear as NEW records with that actionType, not as edits, so this is an append-only event log, not a snapshot.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 3,
      "regulator": "CFTC",
      "asset_class": "IR"
    },
    "name": "dtcc_swaps_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax trades to return, most-recent first (default 20, max ~100, the feed itself only retains the most recent ~100 per bucket).
regulatorYesWhich regulator the swap is reported under: CFTC (commodity/credit/equity/FX/rates), SEC (security-based swaps), or CA (Canadian regulators).
asset_classYesAsset class: CR=credit, EQ=equity, IR=interest-rate, FX=foreign exchange (CFTC only), CO=commodity (CFTC only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max trades to return, most-recent first (default 20, max ~100 — the feed itself only retains the most recent ~100 per bucket)."New value: +"Max trades to return, most-recent first (default 20, max ~100, the feed itself only retains the most recent ~100 per bucket)."
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, yet the description adds substantial semantics beyond them: this is an append-only event log rather than a snapshot, and corrections/cancellations surface as NEW records carrying CORR/EROR/MODI/TERM actionType codes rather than mutating prior rows. That is exactly the kind of trap an agent needs warned about before interpreting results.

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?

Purpose is front-loaded in the first clause, and the appended detail about actionType and append-only semantics earns its space. The second sentence is a long enumeration of regulators and asset classes that partly duplicates the schema enums, making the text denser than necessary.

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?

With no output schema, the description correctly compensates by enumerating the returned record fields (notional, rate terms, dates, product identifiers, actionType). The limit/retention behavior is documented in the schema. The main gap is that it never says where to go for older or bulk history, which the sibling file tool presumably covers.

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 coverage is 100% and each of the three parameters already carries a descriptive string with enum meanings, so the schema does the heavy lifting. The description's mention of covered regulators and asset classes loosely corroborates the regulator/asset_class enums but adds no new constraint or format detail. Baseline 3 is appropriate.

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?

"Most-recently disseminated swap transactions from DTCC's ... real-time price dissemination feed" gives a specific verb, resource, and source. The regulatory and asset-class scope is spelled out. It does not name or contrast with the sibling dtcc_swaps_dissemination_files, so the differentiation is implicit ("live") rather than explicit.

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 defines the domain well enough that an agent can infer this is for current/recent swap activity, but it never states when to prefer it over a file-based or historical alternative, and gives no when-not conditions. Usage is implied by scope, not instructed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.