Skip to main content
Glama

Primary Source Commodities

Mineral Coverage and HS Pairings

minerals.list
Read-onlyIdempotent

Which minerals the dossier covers, the HS code curated for each, and the caveats on comparing supply to trade. FREE. Worth calling before minerals.dossier for two reasons: the cobalt and lithium HS headings exist nowhere else in this API, since trade.codes lists headings only for catalog instruments and neither mineral has one; and the HS code here is chosen to match the USGS production basis, so copper, nickel and zinc point at ore headings rather than the refined-metal headings their instruments use. Also reports which minerals currently have US net import reliance and which column it was read from.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "minerals.list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
editionNoUSGS MCS edition stored
mineralsYesPer mineral: instrument, HS code and level, bases, caveats
not_mappedNoMinerals deliberately refused, with the reason

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, closed-world and non-destructive, so the safety profile needs no restating. The description adds what those annotations cannot: the call is FREE (cost/quota context), the HS codes are a curated choice rather than a mechanical lookup, and the values are meant to be read against a USGS production basis with caveats, not compared naively to trade data. It also says the tool reports which US net import reliance column was read, which pre-empts a provenance question.

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 answer ('Which minerals the dossier covers...') before any justification, and every sentence earns its place because it either describes the fields or explains why this call must precede minerals.dossier. The second sentence is long and semicolon-heavy, so the structure is dense rather than crisp, which is the only thing keeping this off a 5.

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 zero-parameter, read-only lookup with an output schema and a full set of annotations, nothing an agent needs before calling is missing. Provenance (USGS production basis), data gaps (no cobalt/lithium headings elsewhere), cost, and the ordering relative to minerals.dossier are all covered; return shape is documented in the output schema and correctly not repeated.

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?

The tool takes no input parameters (0 params, additionalProperties false), so the baseline of 4 applies and there is no parameter meaning the description could usefully add. Instead of parameter detail, the description spends its words on the semantics of the returned fields (HS heading choice, import-reliance column), which is the right allocation for a zero-argument tool.

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 specific verb and resource: 'Which minerals the dossier covers, the HS code curated for each, and the caveats on comparing supply to trade.' It also tells the agent exactly how it differs from minerals.dossier (call this first) and trade.codes (no cobalt/lithium headings there), so it can be told apart from its siblings without opening any 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 says 'Worth calling before minerals.dossier' and gives the two reasons that select it: unique HS headings for cobalt and lithium, and HS codes aligned to the USGS production basis rather than refined-metal headings. It also names trade.codes as the alternative source of HS headings and explains why that alternative does not apply here.

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