Skip to main content
Glama

Mcs Commodity Data

mcs_commodity_data
Read-onlyIdempotent

U.S. salient statistics for one mineral commodity from the USGS Mineral Commodity Summaries, the most recent 5 years of production, imports, exports, consumption, price, employment, and NET IMPORT RELIANCE (the "import reliance" figure, what share of U.S. consumption comes from imports). Accepts a common name ("lithium", "copper", "rare earths", "platinum group metals") or the MCS code. Raw USGS footnote codes (W=withheld, E=estimated, NA=not available, ">50" on import reliance) are preserved verbatim, never silently coerced to a number. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "commodity": "lithium"
    },
    "name": "mcs_commodity_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
commodityYesCommodity name or code, e.g. "lithium", "cobalt", "rare earths", "gold".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond them: it is keyless (no auth needed) and raw USGS footnote codes (W, E, NA, '>50') are preserved verbatim and never silently coerced to a number, which tells the agent how to interpret results. It does not mention error behavior for unknown commodity names.

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?

The definition is a single dense passage that front-loads the resource and time window before the field list. It is appropriately sized for the information conveyed, though the parenthetical gloss on 'NET IMPORT RELIANCE' is slightly verbose.

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?

With no output schema, the description carries the burden of describing returns, and it does so by enumerating the six statistics plus import reliance over 5 years. The only gap is response structure and behavior on an unrecognized commodity name, which is minor for a one-parameter read 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%, so the baseline is 3. The description goes slightly beyond the schema by emphasizing that either a common name or the MCS code is accepted and by giving richer value examples ('rare earths', 'platinum group metals') than the schema's property description, which materially helps the agent construct valid input.

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 description states a specific verb and resource: returns U.S. salient statistics for one mineral commodity from the USGS Mineral Commodity Summaries, over the most recent 5 years. It enumerates the returned fields (production, imports, exports, consumption, price, employment, net import reliance), and the phrase 'for one mineral commodity' implicitly scopes it against mcs_country_comparison and mcs_list_commodities. An agent can tell what it does 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 Guidelines3/5

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

Usage is implied by the single-commodity scope, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for comparison or listing. The agent must infer that mcs_country_comparison and mcs_list_commodities cover the other cases.

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.