Primary Source Commodities

Latest Price

price.latest

Read-onlyIdempotent

Return the latest cash/fundies observation for one instrument code. Use catalog.list to discover codes such as CL, GC, or ZC. Response follows the shared observation contract with provenance and license tags.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Stable observation id
`name`	Yes	Human-readable instrument name
`unit`	Yes	Unit of measure
`as_of`	Yes	As-of date for the observation
`value`	Yes	Observed numeric value
`inputs`	No	Input series ids when derived
`source`	Yes	Primary source provenance
`derived`	Yes	True when value is derived
`formula`	No	Derivation formula when derived
`quality`	Yes	Data quality label
`raw_hash`	No	Hash of raw source payload
`series_id`	Yes	Underlying series id
`instrument`	Yes	Instrument code, e.g. CL
`provenance`	Yes	Retrieval / cache provenance
`license_tag`	Yes	License / redistribution tag
`observed_at`	Yes	ISO timestamp when observed
`freshness_class`	Yes	Freshness class for the series

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 indicate read-only, idempotent, non-destructive behavior. Description adds that response follows a shared observation contract with provenance and license tags, 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, each with distinct purpose: stating functionality and guiding code discovery. No extraneous information.

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?

Tool is simple with one parameter, has output schema (not shown), and description covers all essential aspects: purpose, code sourcing, and response contract.

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 has 100% coverage of the single parameter. Description adds value by explaining the code comes from catalog.list and provides examples (CL, GC, ZC), aiding selection.

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 returns the latest observation for one instrument code, differentiating it from price.history (returns history) and catalog.list (discovers codes).

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 advises to use catalog.list to discover instrument codes, providing clear context for when to use this tool versus its sibling.

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?