catalog.listList every commodity instrument in the catalog with sector, unit, primary source, and freshness metadata. Call this first to discover valid codes before price.latest or inventory.get. Free discovery tool — no payment required.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| instruments | Yes | Instrument registry rows |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, destructiveHint. Description adds extra transparency about being free and including freshness metadata. 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences: first states purpose, second gives usage guidance. Front-loaded, no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no parameters, output schema exists. Description covers purpose, output fields, usage context, and hints. Fully adequate for a zero-parameter discovery tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has no parameters (0 params, 100% coverage). Description adds value by listing output fields (sector, unit, primary source, freshness), beyond schema. Baseline 4, elevated for helpful output info.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'List every commodity instrument in the catalog' with specific attributes (sector, unit, primary source, freshness). Distinguishes from siblings by advising to 'Call this first to discover valid codes before price.latest or inventory.get.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit guidance on when to use: 'Call this first...before price.latest or inventory.get.' Also mentions it's a free discovery tool with no payment required, adding context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.