Skip to main content
Glama
Sign In

Ava Advisor

by fund.ava
OverviewDiscussionsAdmin

CFTC / COT Futures Extremes

cot_extremes
Read-only

⭐ FUTURES / CFTC-COT speculative positioning extremes — which commodity / FX / rate / equity-INDEX FUTURES have the CROWD at a 3-year extreme right now (NOT single-stock equity options → for 'stretched put/call' or crowded STOCK names use options_scan). The discovery scan across every tracked futures market at once. COT / FUTURES lens ONLY. Surfaces stretched positioning (≥90th or ≤10th percentile of its own 3y history) that could unwind hard on a shock — a contrarian-RISK map, NOT buy/sell calls (an extreme can persist). Use for 'where is FUTURES positioning most crowded / stretched right now?'. 🔴 WRONG TOOL for single-STOCK options crowding — 'stretched put/call', 'one-sided / crowded equity names', 'most extreme options positioning across stocks': for those use options_scan (pattern='crowded / one-sided' — the equity-options opana lens across ~557 US optionable names). Narrate each read plainly.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax markets (default 15, max 50).
asset_classNoFilter: `commodity` | `fx` | `rates` | `equity_index`. Omit = all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=true already covers safety, and the description adds real behavioral context: the extreme is defined as ≥90th or ≤10th percentile of each market's own 3-year history, and results are a contrarian risk map rather than signals. It even hints at a per-row 'read' field to narrate. Missing only things like result count behavior or data freshness.

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

Conciseness3/5

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

The core purpose and exclusion are front-loaded, which is good, but the text is padded with all-caps shouting and repeated restatements of 'COT / FUTURES lens ONLY', 'NOT single-stock options', and the equity-options warning twice in near-identical form. It is longer than it needs to be for two optional parameters.

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 two-optional-parameter read-only scan with no output schema, the description covers scope, the percentile definition, the interpretation caveat, and the sibling routing. An agent has enough to call it correctly and read the results sensibly.

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 both parameters are documented there, including the default-15/max-50 limit and the asset_class enum values. The description adds nothing parameter-specific beyond that, so the baseline 3 applies.

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?

Names a specific verb-and-resource: a discovery scan of CFTC/COT speculative positioning extremes across all tracked futures markets. It explicitly scopes the asset space (commodity / FX / rate / equity-index futures, not single stocks) and names the sibling that handles the excluded case.

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?

Gives an explicit when-to-use trigger ('where is FUTURES positioning most crowded / stretched right now?') and an explicit when-NOT-to-use rule with the exact alternative (options_scan with pattern='crowded / one-sided'). It also warns the output is not actionable buy/sell calls because an extreme can persist.

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

All Ava Advisor 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