Skip to main content
Glama

Primary Source Commodities

Critical Minerals Supply and Trade

minerals.dossier
Read-onlyIdempotent

Who mines a mineral, who holds its reserves, and who exports it — USGS Mineral Commodity Summaries production and reserves by country, joined to UN Comtrade export flows and realised unit values, with supply concentration and US net import reliance. REFUSES three things: no ratio between the supply side and the trade side, because USGS counts contained metal while HS counts the gross weight of a traded article and for lithium those differ by about five times; no price of any kind; no criticality or supply-risk score. EXPORTS ARE NOT PRODUCTION — for gold and silver the largest reporters refine and vault rather than mine, so the two halves rank different countries for good reasons. The HS code matches the USGS production basis, so copper, nickel and zinc point at ore and concentrate headings rather than the refined-metal headings their instruments use. Annual data. Paid.

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": {
      "mineral": "<mineral>"
    },
    "name": "minerals.dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoTrade year for the Comtrade half. USGS years are fixed by the edition.
limitNoMaximum country rows.
mineralYesWhich mineral. Required.

Output Schema

NameRequiredDescriptionDefault
notesYes
tradeNoComtrade exports; null when the licence is unresolved
supplyNoUSGS production and reserves, in the mineral's own unit
mineralYes
countriesYesPer-country supply and trade, largest producer first
instrumentNoCatalog instrument where one quotes this metal; null for cobalt and lithium
comparabilityYesWhether the two sides may be compared at all
concentrationYesTop-3 share and HHI per side, with formula and coverage
net_import_relianceNoUS only, with the column it was read from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world behavior, but the description adds substantial context beyond that: annual frequency, a paid tier, the contained-metal vs gross-weight mismatch (~5x for lithium), and the HS-code basis aligning copper/nickel/zinc to ore and concentrate headings. These are exactly the traps that would cause a misread of the results.

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 core capability is front-loaded in the first sentence, followed by exclusions and caveats in priority order. It is dense and uses capitalized emphasis that borders on verbose, but nearly every sentence carries a decision-relevant caveat.

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 multi-source join tool, the description covers the data provenance, the join hazard, the unit-basis hazard, the HS-code alignment, frequency, and cost. An output schema exists, so return-value explanation is not required, and nothing an agent needs to call it correctly is missing.

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%, so the year, limit, and mineral parameters are already documented, including the distinction between trade year and fixed USGS edition years. The description adds only 'Annual data' as a frequency note and does not clarify limit behavior or year defaults beyond 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 description names the specific resource set — USGS production and reserves by country, joined to Comtrade export flows and realised unit values, plus supply concentration and US net import reliance — with concrete verbs ('who mines', 'who holds', 'who exports'). This is clearly distinguishable from price, flow, and ranking siblings.

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?

It gives explicit when-not-to-use conditions: no ratio between supply and trade halves, no price of any kind, no criticality score, and it warns that exports are not production. It stops short of naming the alternative tools (price.latest, trade.flow) for the refused use cases, leaving the agent to infer the routing.

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