Primary Source Commodities

COT Positioning

positioning.get

Read-onlyIdempotent

Return the latest CFTC Commitments of Traders managed-money positioning for an instrument code. Includes long, short, net, and week-over-week net change with source URL.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	Instrument code from catalog.list. Example: CL, NG, GC, ZC.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	COT row id
`mm_net`	Yes	Managed-money net contracts
`mm_long`	Yes	Managed-money long contracts
`mm_short`	Yes	Managed-money short contracts
`instrument`	Yes	Instrument code
`source_url`	Yes	CFTC source URL
`observed_at`	Yes	ISO timestamp when observed
`report_date`	Yes	CFTC report date
`mm_net_change`	Yes	Week-over-week change in managed-money net
`commodity_name`	Yes	CFTC commodity name

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds that it returns 'latest' data and includes source URL, providing useful context beyond annotations. No contradiction.

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?

Two sentences, no filler, front-loaded with the core purpose. Every word adds value.

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?

Output schema exists, so return values are documented elsewhere. Tool is simple (one parameter, read-only, idempotent). Description covers all needed usage context.

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% for the single parameter 'code'. Description adds example values (CL, NG, GC, ZC) and source (catalog.list), which improves usability beyond the schema's basic description.

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?

Description clearly states the verb (return), resource (latest CFTC COT managed-money positioning for an instrument code), and specific data included (long, short, net, week-over-week net change with source URL). Distinguishes from siblings as a unique data retrieval tool.

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?

Description implies use when needing CFTC positioning data. No explicit when-not or alternatives, but context makes purpose clear. Could benefit from mentioning that this tool is for managed-money only, not all traders.

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

All Primary Source Commodities tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool has a distinct purpose: calendar.get for release dates, catalog.list for instrument discovery, price.latest and price.history for prices, inventory.get for inventory, positioning.get for CFTC data, fundamentals.get for reports, fx.latest for FX rates, snapshot.get for sector overview, spread.get for derived spreads, and decision.get for deterministic decisions. No overlapping functionality.

Naming Consistency5/5

All tools follow a consistent noun.verb pattern (e.g., calendar.get, catalog.list, price.latest, snapshot.get). The naming is predictable and makes the tool's purpose clear at a glance.

Tool Count5/5

With 11 tools, the server is well-scoped for a commodity data platform. Each tool covers a distinct aspect (calendar, catalog, prices, inventory, positioning, fundamentals, FX, snapshots, spreads, decisions) without unnecessary bloat.

Completeness4/5

The tool set covers core commodity data needs: price discovery (catalog, latest, history), fundamentals (WASDE, etc.), inventory (EIA), positioning (CFTC), spreads, FX conversion, and summaries. Minor gaps include limited price history (500 points) and no explicit support for options or shipping data, but the overall surface is strong.

Resources

Need Help?