Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

CFTC Commitments of Traders, latest weekly report in one call: per futures market open interest, non-commercial (specula

cot
Read-onlyIdempotent

CFTC Commitments of Traders, latest weekly report in one call: per futures market open interest, non-commercial (speculator) long/short and net, commercial long/short and net; filter market=<name contains, e.g. GOLD, CRUDE, S&P, BITCOIN>, count up to 50 ordered by open interest. Pay per call $0.002 USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cot"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoup to 50
marketNoname contains, e.g. GOLD, CRUDE, BITCOIN
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior. The description adds important non-schema context: the tool returns the latest weekly report, orders results by open interest, and costs $0.002 USDC per call on Base via x402. It does not discuss latency or freshness beyond 'latest weekly', but the payment and ordering details are material additions.

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 a single dense, front-loaded sentence that covers purpose, fields, filtering, ordering, and payment. It is efficient, though the run-on structure and repetition of the title make it slightly harder to parse than a shorter split presentation would be.

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?

There is no output schema, so the description carries the burden of explaining what is returned, and it does so by listing the per-market metrics. Payment requirements are covered enough for an agent to know the first call can be made without payment and that successful calls cost USDC via x402, though it could say more about exactly how partial payment failures are surfaced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by specifying that market uses substring matching ('name contains') with concrete examples and that count results are ordered by open interest. The schema already documents count as 'up to 50,' so the added value is modest but real.

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 names the exact dataset (CFTC Commitments of Traders) and enumerates the returned fields per market: open interest, non-commercial long/short/net, and commercial long/short/net. This is a specific resource with a clear verb-like scope ('latest weekly report in one call'), making it distinguishable from the unrelated sibling tools.

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?

It defines how to use the tool: filter with market=<name contains> using examples such as GOLD, CRUDE, S&P, and BITCOIN, and cap results with count up to 50 ordered by open interest. There are no explicit when-not or alternative-tool conditions, but the usage context is clear and no sibling overlaps with this dataset.

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.

Resources