Skip to main content
Glama

Cftc Cot

by io.github.pipeworx-io
OverviewAdmin

Search Markets

search_markets
Read-onlyIdempotent

Find CFTC Commitment of Traders (COT) futures markets by name. Use this first to get the exact market_and_exchange_names and contract_code that latest_report and report_history require. Keyless. e.g. "crude oil", "gold", "E-MINI S&P", "bitcoin", "euro", "corn".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax distinct markets to return (default 15, max 30).
queryYesSubstring to match against the market name, e.g. "crude oil", "gold", "E-MINI S&P", "bitcoin", "euro".

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "crude oil"
+  },
+  {
+    "limit": 10,
+    "query": "gold"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive). Description adds 'Keyless' and clarifies substring matching behavior, providing useful context beyond annotations.

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 concise sentences with examples. No wasted words; key information is front-loaded.

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 search tool with no output schema, description explains purpose, input requirements, and downstream usage. Could mention result format or pagination, but sufficient for typical use.

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 baseline is 3. Description adds example values, clarifies query is substring match, and explains limit default and max, adding meaningful guidance.

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 it finds CFTC COT futures markets by name, with specific verb and resource. It distinguishes from sibling tools by noting it provides inputs needed for latest_report and report_history.

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?

Explicitly says 'Use this first' to get required names for later tools. Provides examples but does not explicitly state when not to use it or list alternatives beyond the two downstream tools.

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

All Cftc Cot toolsInspect
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.

Resources