Skip to main content
Glama

FinanceQuery

Commodity Quote

get_commodity
Read-onlyIdempotent

Get a commodity's current quote (e.g. gold, silver, crude oil), provider-routed (Yahoo, keyless).

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": {
      "symbol": "<symbol>"
    },
    "name": "get_commodity"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesCommodity symbol (e.g. "GCUSD" for gold, "CLUSD" for crude oil)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine context beyond that with 'provider-routed (Yahoo, keyless)', telling the agent the data source and that no API key is needed. It does not disclose whether quotes are real-time or delayed, nor any rate limits or fallback behavior when Yahoo fails.

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?

A single front-loaded sentence with the verb and resource first and the provider note trailing. No filler, no repetition of the title, and every clause carries information.

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 two-parameter read-only quote tool with full schema coverage and complete annotations, the description covers purpose, scope and provider behavior adequately, and no output schema means return values need not be explained. The only meaningful gap is quote freshness (real-time vs delayed), which matters for a price lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are documented, including symbol examples (GCUSD, CLUSD) and the fields parameter's comma-separated semantics. The description's commodity examples (gold, silver, crude oil) add only marginal meaning over the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get a commodity's current quote') and names example commodities, which separates it by asset class from siblings like get_crypto and get_forex. It stops short of distinguishing itself from get_quote or get_futures, so an agent cannot fully resolve the commodity-vs-futures boundary from this text alone.

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

Usage Guidelines3/5

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

Usage is only implied: the asset-class examples suggest when to reach for this tool, but there is no explicit when-to-use statement, no exclusion, and no named alternative such as get_futures for contracts. Adequate but leaves the sibling choice to inference.

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.