Skip to main content
Glama

Trading Signals Toolkit

CFTC COT Positioning Screener

cot_screener
Read-only

Weekly CFTC Commitments of Traders screener across 45 futures markets (equity indexes, VIX, Treasuries, SOFR, crude, natgas, gold, silver, copper, grains, livestock, softs, FX, BTC, ETH): large-speculator net position, % of open interest, weekly change, 3-year percentile, crowded_long / crowded_short flags, biggest weekly shifts and net flips, plus the next release time. Read-only, never places orders. Informational only, not investment advice.

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_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
extremeNotrue = only markets flagged crowded_long or crowded_short
symbolsNoComma list, e.g. ES,NQ,GC,CL,ZN,6E,BTC
thresholdNoPercentile that counts as crowded (default 90)
assetClassNoComma list: equity_index, volatility, rates, energy, metals, grains, livestock, softs, fx, crypto

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, it discloses the weekly cadence, three-year percentile lookback, detection of shifts and net flips, and inclusion of the next release time. The read-only/no-orders statement is consistent but largely repeats the safety annotations; report lag, release timezone, and similar external-data timing details remain unspecified.

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 purpose and market scope are front-loaded, and the three sentences contain little filler. However, the opening sentence is overloaded with exhaustive market and output inventories, while "Read-only" and "never places orders" are somewhat redundant.

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?

For a simple read-only tool with four optional filters and no output schema, it covers the source, scope, cadence, principal returned fields, crowding outputs, and release timing, while the schema documents filter defaults and formats. It could still clarify default result scope and ordering, how many "biggest" shifts are returned, and report/as-of timestamp conventions.

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?

All four parameters are already documented in the schema, so the description starts from an adequate baseline. It adds the three-year basis for the percentile underlying threshold and exposes the exact crowded_long/crowded_short flag vocabulary, modestly helping interpret the extreme filter without needing to repeat filter syntax.

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 identifies the exact dataset, weekly cadence, 45-market futures universe, and concrete outputs such as large-speculator net positioning, three-year percentiles, and crowding flags. This source-and-output specificity makes its niche unambiguous and distinguishes it semantically from the siblings without requiring an explicit comparison.

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 wording implies use for weekly positioning, crowding, and shift analysis, but it never states when to choose this tool or when another tool would be preferable. "Informational only, not investment advice" is a disclaimer rather than selection guidance, and the weekly scope is not explicitly presented as a limitation for intraday questions.

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