Skip to main content
Glama

Oxford Ledge

by com.oxfordledge
OverviewDiscussionsAdmin

CFTC Commitments of Traders

ol_cftc_cot
Read-only

CFTC Commitments-of-Traders positioning for THREE curated markets (keys gold, crude_oil, sp500). Pass market for its weekly history, NEWEST FIRST (names are normalised: 'wti', 'GOLD', 'e-mini s&p' resolve), or omit it for the latest report across the three. Returns {summary, market, matched_market, rows}. mm_* and open_interest are CONTRACT counts, not dollars, and mm_* cover ONE speculative category per report family (Managed Money for gold and crude_oil, Leveraged Funds for sp500). limit (series only) default 52, hard cap 156. An unreachable store is REFUSED (DATA_UNAVAILABLE). Source: CFTC.gov (public domain); FREE. ATTRIBUTION: every field is CFTC verbatim EXCEPT market_key and market_label (Oxford Ledge's curated market catalog) and mm_net (mm_long minus mm_short, computed by Oxford Ledge).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoWeekly reports for a market series (default 52, hard cap 156).
marketNoMarket key, CFTC report name or desk symbol -- gold / GC / XAU, crude_oil / CL / WTI, sp500 / ES / S&P (case-insensitive; omit for the latest all-market snapshot).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only mark readOnlyHint, so the description carries the behavioral burden; it discloses ordering (NEWEST FIRST), return keys, unit semantics (CONTRACT counts, one category per family), limit defaults/caps, and DATA_UNAVAILABLE refusal. Rich and non-contradictory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with scope and market keys, then proceeds through usage, return shape, units, limit, errors, and attribution. Dense but every sentence adds needed context for a financial data tool; no obvious filler.

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?

Given two optional params, no output schema, and readOnly annotation, the description covers all an agent needs: valid markets, alias handling, ordering, units, limits, and error behavior. Complete.

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%, so the schema already documents both parameters. The description adds alias examples and clarifies `limit` applies only to series, but most semantics are already in the schema; 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?

States a specific dataset (CFTC Commitments-of-Traders positioning) and the exact curated markets (gold, crude_oil, sp500), so an agent can tell it apart from generic financial siblings. The verb 'Pass/omit' clarifies the operation.

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?

Explains when to pass `market` (weekly history) vs omit it (latest all-market snapshot), and documents alias resolution. It does not name alternative tools or when-not to use this one, so 4 rather than 5.

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

All Oxford Ledge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources