Skip to main content
Glama

veroq_alt_cot

Retrieve CFTC Commitment of Traders data for a commodity. Shows net positions of commercial hedgers, large speculators, and small traders to identify extreme positioning that may precede market reversals.

Instructions

CFTC Commitment of Traders positioning for a commodity.

WHEN TO USE: To see how commercial hedgers, large speculators, and small traders are positioned in futures markets. A contrarian indicator — extreme positioning often precedes reversals. RETURNS: Net positions by trader category, open interest, and changes from prior week. COST: 1 credit. EXAMPLE: { "commodity": "gold" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commodityYesCommodity name (e.g. gold, silver, crude-oil, natural-gas, corn, soybeans, wheat, copper, sp500)
Behavior3/5

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

No annotations provided, so the description carries full burden. It discloses the return type and cost, but lacks details on data update frequency (weekly), error conditions, or any behavioral nuances. Adequate but not comprehensive.

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?

Exceptionally concise and well-structured with clear sections: purpose, when to use, returns, cost, and example. Every sentence earns its place with no wasted words.

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?

Given no output schema, the description provides sufficient context: it states the return fields (net positions, open interest, changes) and cost. Slightly lacking in specifying data frequency (weekly) but still fairly complete for a simple tool.

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?

Input schema has 100% coverage with a description listing examples. The tool description only adds an example call with 'gold', which is already implied by the schema. Minimal added value beyond the schema.

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?

The description clearly states it provides CFTC Commitment of Traders positioning for a commodity, with specific output details. While not explicitly differentiating from sibling tools like veroq_commodities, the purpose is distinct and unambiguous.

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?

Includes a 'WHEN TO USE' section that explains the tool's utility for viewing futures market positioning and notes its role as a contrarian indicator. However, it lacks explicit when-not-to-use guidance or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Veroq-ai/veroq-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server