Skip to main content
Glama

Usgs Cmd Deposits Search

usgs_cmd_deposits_search
Read-onlyIdempotent

Search USGS's "Critical mineral deposits of the United States" database (ver. 3.0, September 2026), 1,271 documented deposits across 41 states + Puerto Rico. Filter by commodity (e.g. "lithium", "cobalt", "rare earth elements"), US state/territory abbreviation, and/or a bounding box. Returns each deposit's id, name, state, coordinates, minerals, deposit type, and resource figures. AUTHORITATIVE for "where are US lithium/cobalt/REE deposits" and "which critical mineral deposits are in ". Sourced from USGS.

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": {
      "state": "AR",
      "commodity": "lithium"
    },
    "name": "usgs_cmd_deposits_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxNoBounding box "minLon,minLat,maxLon,maxLat" (WGS84), e.g. "-120,34,-115,37".
limitNoMax deposits to return (default 25, max 100).
stateNoUS state or territory 2-letter abbreviation, e.g. "CA", "AK", "PR".
commodityNoCritical mineral/commodity, e.g. "lithium", "cobalt", "ree", "copper". Matched against the dataset's own commodity vocabulary (not a canonical element list), an unmatched value returns found:false with the full commodity list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / commodity / description
      Previous value: -"Critical mineral/commodity, e.g. \"lithium\", \"cobalt\", \"ree\", \"copper\". Matched against the dataset's own commodity vocabulary (not a canonical element list) — an unmatched value returns found:false with the full commodity list."New value: +"Critical mineral/commodity, e.g. \"lithium\", \"cobalt\", \"ree\", \"copper\". Matched against the dataset's own commodity vocabulary (not a canonical element list), an unmatched value returns found:false with the full commodity list."
  2. 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 the safety profile is covered. The description adds useful context beyond that: dataset version and date (ver. 3.0, September 2026), record counts, and the found:false fallback with the full commodity list when a commodity doesn't match. It says nothing about result ordering or what happens when limit truncates matches.

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 dataset identity and scope, then the return fields, then the usage claims – a sensible order with no filler sentences. The AUTHORITATIVE phrasing is a little promotional but carries routing 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?

With no required parameters, four fully documented optional filters, and four annotations, the description covers what an agent needs to call it and what it will get back. Remaining gaps (ordering, truncation messaging, the found:false envelope shape) are minor since no output schema exists to carry them.

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 schema already documents all four parameters including bbox format, state abbreviations, and limit bounds. The description only restates the filter axes (commodity, state, bbox) and adds a few commodity examples, providing marginal meaning beyond the schema.

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?

The description names a specific verb ("Search") and resource ("USGS's Critical mineral deposits of the United States database") and quantifies scope (1,271 deposits, 41 states + Puerto Rico) plus the fields returned. It doesn't explicitly differentiate from the sibling usgs_cmd_deposit_detail, which is the only reason it falls short of a 5.

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 query classes the tool is authoritative for ("where are US lithium/cobalt/REE deposits", "which critical mineral deposits are in <state>"), which tells the agent when to reach for it. It stops short of stating when NOT to use it or naming the detail tool as the alternative for single-record lookups.

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.