Skip to main content
Glama
screener-mcp
by LogeshR15

get_commodity_prices

Read-only

Tracks international benchmark commodity prices with 4-week, 52-week, and multi-year moves, USD/INR conversion, and Indian listed companies exposed to price changes.

Instructions

Commodity price context and its impact on Indian listed companies.

Returns the international benchmark price the MCX/NCDEX contract tracks (COMEX gold/silver/copper, Brent, Henry Hub, CBOT wheat, etc.), with 4-week, 52-week and years-period moves and range, USD/INR, and an approximate INR price (a pure FX conversion — excludes import duty/GST, so below MCX). Also lists which companies benefit or suffer from price moves and their symbols (data.watch_symbols) to pass to compare_companies.

commodity: gold | silver | crude_oil | copper | aluminium | zinc | nickel | cotton | natural_gas | steel | wheat | tobacco | wood_pulp (nickel, tobacco, wood_pulp: no free price feed → partial, exposure analysis only) years: history period for the moves and range (1–10, default 5)

Examples: get_commodity_prices("crude_oil") get_commodity_prices("copper", years=3) get_commodity_prices("gold")

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": {
      "commodity": "<commodity>"
    },
    "name": "get_commodity_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNo
commodityYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only say readOnlyHint and openWorldHint, but the description adds real behavioral context: the INR figure is 'a pure FX conversion — excludes import duty/GST, so below MCX', and nickel/tobacco/wood_pulp return 'partial, exposure analysis only' because there is no free price feed. That is exactly the kind of caveat an agent needs before trusting the numbers; only the lack of any staleness/rate-limit note keeps it from a 5.

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 one-sentence purpose, then scoped details, then a compact parameter list and three call examples. Every block carries information, though the examples largely restate the enum and the parameter list, so it runs slightly longer than strictly necessary.

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?

For a two-parameter read-only tool with an output schema, this covers everything material: what is returned, currency caveats, partial-data commodities, the full value set, and the downstream tool to use. No gap an agent would need to resolve before calling it correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry the parameters, and it does: it enumerates all 13 accepted commodity values (which the schema does not constrain via enum) and flags the three that degrade to exposure-only. It also defines `years` as the 'history period for the moves and range (1–10, default 5)', supplying both semantics and bounds absent from the schema.

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?

The opening sentence plus the follow-up 'Returns the international benchmark price the MCX/NCDEX contract tracks... with 4-week, 52-week and years-period moves and range, USD/INR, and an approximate INR price' gives a precise verb-plus-resource statement and enumerates the actual outputs. It also distinguishes the tool from compare_companies by naming the handoff, so an agent can identify it without opening the schema.

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?

Usage is clearly implied (get benchmark price context and the companies exposed to it) and the description explicitly routes the agent onward: the listed symbols are 'to pass to compare_companies'. It stops short of stating when NOT to use it or naming other alternatives, so it is clear context rather than full when/when-not guidance.

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