Skip to main content
Glama

deposits

Read-only

Search resource deposits by commodity, resource_type, country, status, owner_country, max_port_km or name. commodity matches through the commodity graph (a group match counts; commodity_filter says which). Returns {count, total, deposits[]}, paged. Metered: see CHARGING in the server instructions; quote first with billing_quote.

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": "deposits"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return. Up to 100. Default 50.
fieldsNoOnly these keys in each row (plus id). Omit for all.
offsetNoRows to skip, for paging. Default 0.
searchNoPart of the deposit's name (substring).
statusNoDeposit status, e.g. operating, development, exploration.
countryNoCountry as an ISO code or a name.
commodityNoA commodity name, e.g. "neodymium".
max_port_kmNoOnly deposits within this many km of a port.
owner_countryNoCountry of the deposit's owners (their home states), ISO code or name.
resource_typeNoThe deposit's primary resource label (exact, case-insensitive).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • removedInput schema / properties / commodity / default
      Removed value: -null
    • changedInput schema / properties / commodity / description
      Previous value: -"A commodity name, e.g. \"neodymium\". Filters by the commodity GRAPH: matches deposits that contain it directly or contain a group it belongs to (so neodymium returns every rare-earth deposit)."New value: +"A commodity name, e.g. \"neodymium\"."
    • removedInput schema / properties / commodity / title
      Removed value: -"Commodity"
    • removedInput schema / properties / country / default
      Removed value: -null
    • removedInput schema / properties / country / title
      Removed value: -"Country"
    • addedInput schema / properties / fields
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Only these keys in each row (plus id). Omit for all."
      +}
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / max_port_km / default
      Removed value: -null
    • removedInput schema / properties / max_port_km / title
      Removed value: -"Max Port Km"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / owner_country / default
      Removed value: -null
    • removedInput schema / properties / owner_country / title
      Removed value: -"Owner Country"
    • removedInput schema / properties / resource_type / default
      Removed value: -null
    • removedInput schema / properties / resource_type / title
      Removed value: -"Resource Type"
    • removedInput schema / properties / search / default
      Removed value: -null
    • removedInput schema / properties / search / title
      Removed value: -"Search"
    • removedInput schema / properties / status / default
      Removed value: -null
    • removedInput schema / properties / status / title
      Removed value: -"Status"
    • removedInput schema / title
      Removed value: -"depositsArguments"
    • removedOutput schema / title
      Removed value: -"depositsDictOutput"
  2. Changed9 schema fields changed
    • addedInput schema / properties / commodity / description
      Added value: +"A commodity name, e.g. \"neodymium\". Filters by the commodity GRAPH: matches deposits that contain it directly or contain a group it belongs to (so neodymium returns every rare-earth deposit)."
    • addedInput schema / properties / country / description
      Added value: +"Country as an ISO code or a name."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return. Up to 100. Default 50."
    • addedInput schema / properties / max_port_km / description
      Added value: +"Only deposits within this many km of a port."
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip, for paging. Default 0."
    • addedInput schema / properties / owner_country / description
      Added value: +"Country of the deposit's owners (their home states), ISO code or name."
    • addedInput schema / properties / resource_type / description
      Added value: +"The deposit's primary resource label (exact, case-insensitive)."
    • addedInput schema / properties / search / description
      Added value: +"Part of the deposit's name (substring)."
    • addedInput schema / properties / status / description
      Added value: +"Deposit status, e.g. operating, development, exploration."
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description adds things annotations cannot: result shape {count, total, deposits[]}, pagination, cost metering with a pointer to CHARGING, and that `commodity` traverses a commodity graph where group matches can be included. That graph-matching behavior is a non-obvious trait an agent would otherwise get wrong.

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?

Three tight sentences, filter list front-loaded, return shape and billing note after. No filler. The one flaw is the dangling `commodity_filter` reference, which costs a bit of clarity in an otherwise economical definition.

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 an output schema available the description need not explain return values, yet it summarizes them, and it flags the metered cost model that any caller must know before invoking. The unexpanded `commodity_filter` mention is the only loose end for a 10-parameter tool with no required params.

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 baseline is 3, but the description adds real meaning: it explains that `commodity` resolves through a graph and that a group match counts, which the schema's "A commodity name" line does not convey. Minor deduction because it references `commodity_filter`, which is not present in the input schema at all, creating ambiguity.

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?

States a specific verb and resource ("Search resource deposits") and enumerates the actual filter axes, so an agent knows precisely what this retrieves. It does not, however, differentiate itself from the singular `deposit`, `deposit_brief`, or `nearby` siblings, leaving the agent to infer that this is the multi-row search variant.

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?

The metering workflow is spelled out ("quote first with `billing_quote`"), which is a genuine usage rule. But there is no statement about when to pick `deposits` over `deposit`, `deposit_brief`, or `nearby`, and no exclusions or prerequisites beyond the billing note.

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