calendar.getList EIA, USDA, and CFTC release calendar entries with cadence, typical Eastern time, and next-hint notes. Free discovery tool — call before scheduling agents around inventory or WASDE prints.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| events | Yes | Upcoming / recurring release events |
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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the tool's safety profile is clear. The description adds context by noting it is a 'free discovery tool' with 'next-hint notes,' but does not elaborate on any additional behavioral traits beyond what annotations provide.
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?
The description is two sentences, front-loaded with key agencies and data types, and no wasted words. It efficiently conveys the tool's function and value without redundancy.
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?
Given the existence of an output schema (not shown but referenced), the description appropriately describes the output contents (cadence, Eastern time, next-hint notes) and the tool's free nature. For a parameterless listing tool, this is fully complete and aligned with the schema.
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?
With zero parameters, schema coverage is 100%, so baseline is 4. The description does not need to explain parameters and correctly omits them, focusing instead on the tool's output and usage context.
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?
The description clearly states the tool lists release calendar entries from specific agencies (EIA, USDA, CFTC) and details the information provided (cadence, typical Eastern time, next-hint notes). It differentiates itself from sibling tools like inventory.get or fundamentals.get by focusing on calendar timing, making the purpose highly specific and actionable.
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?
The description advises to call before scheduling agents around inventory or WASDE prints, providing clear context when to use. It does not explicitly mention when not to use or compare to alternatives, but the guidance is direct and relevant for the intended use case.
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.