Skip to main content
Glama

Primary Source Commodities

Latest Prices for Several Instruments

price.bundle
Read-onlyIdempotent

The latest observation for up to 20 instruments in ONE call. A separate tool from price.latest rather than an optional argument on it, because the two are priced differently and nothing binds a payment to a request body — one multiplexed entry point would let a caller quote the single price and send the bundle. Use this instead of looping price.latest: it is one settlement and one round trip. Codes that do not resolve come back with an error field rather than being dropped, and codes past the cap are listed in dropped_codes. Paid; charged only if at least one code resolves.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "codes": "<codes>"
    },
    "name": "price.bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYesInstrument codes, up to 20. Example: ["CL", "BZ", "HG"].

Output Schema

NameRequiredDescriptionDefault
countYes
observationsYes
dropped_codesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds behavior annotations cannot express: it is paid and charged only if at least one code resolves, unresolvable codes return an error field instead of being silently dropped, and codes beyond the cap surface in dropped_codes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the sibling contrast, then the settlement/pricing notes. The middleware-rationale sentence about payment binding to a request body is developer justification that an invoking agent does not need, though it is short enough not to bury the operative guidance.

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 need not be spelled out, and the description still flags the two result fields that matter operationally (per-code error, dropped_codes). Cost model, cap, and alternatives are all present for a one-parameter tool.

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% and the single 'codes' parameter is already documented, so baseline is 3. The description adds failure semantics for those codes — per-code errors rather than silent drops, and a dropped_codes list past the 20 cap — which meaningfully extends how the caller should build the array.

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?

States a concrete verb and resource — 'latest observation for up to 20 instruments in ONE call' — and immediately distinguishes itself from price.latest by name, so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes usage: 'Use this instead of looping price.latest' and names price.latest as the alternative for the single-code case. The rationale for two separate tools is given, so the agent knows why the choice matters rather than just that it exists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources