Skip to main content
Glama

deposits

Search resource deposits (relays GET /api/v1/deposits). Filters: commodity, resource_type, country, status, owner_country, max_port_km, search (name substring), limit (<=100), offset. ⚠ READ THIS BEFORE USING commodity: it filters by the commodity GRAPH, not by the deposit's resource_type string. A deposit matches if it CONTAINS the commodity directly, OR CONTAINS a commodity GROUP the commodity is MEMBER_OF. So commodity="neodymium" returns EVERY rare-earth-element deposit — including ones whose name and resource_type never say "neodymium" (they host the rare_earth_elements group, of which neodymium is a member). That is correct, not a broken filter. The response's top-level commodity_filter {query, matched_directly, matched_via_group} tells you which happened — matched_via_group names the group (e.g. "rare_earth_elements") when the match came through it. Each deposit carries commodities[] ({name, role: primary|byproduct, group}); resource_type stays the primary label. Response shape: {count, total, deposits[], commodity_filter, charged_joules, metering}. Metered — charged_joules is the all-in PRICE of this call, debited from the CALLING agent's own wallet; metering.settlement / metering.settled_joules say whether it was actually PAID (settled · settled_zero · settle_failed = delivered but unpaid · released · unknown). Quote first with billing_quote("/api/v1/deposits"). Same as the SDK deposits(commodity=...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
searchNo
statusNo
countryNo
commodityNo
max_port_kmNo
owner_countryNo
resource_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the full burden, and it does so exceptionally. It discloses the graph-based commodity matching behavior, the metered nature of the call, that charged_joules is debited from the caller's wallet, and the settlement states. It also explains the response's commodity_filter field to preempt confusion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but dense, and every section earns its place: purpose, filter list, critical commodity warning, response shape, and metering/billing. The most important caveat is prominently flagged with '⚠ READ THIS BEFORE USING `commodity`', making the structure effective despite the length.

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?

Given 9 parameters, zero schema descriptions, no annotations, and an output schema that is not shown, the description is remarkably complete. It covers all parameters, the response shape, the anomalous commodity behavior, and the financial consequences of calling the tool, providing an agent everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description compensates fully by naming every parameter and adding semantic meaning: search is a name substring, limit is capped at 100, and commodity has a non-obvious graph matching behavior with a detailed example. This goes far beyond the schema's bare type information.

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 opens with a specific verb and resource: 'Search resource deposits (relays GET /api/v1/deposits).' It clearly identifies the tool's scope and differentiates it from the sibling singular 'deposit' tool by focusing on plural search behavior.

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?

The description makes the search context explicit and enumerates all filters, clearly establishing when this tool is appropriate for listing/filtering deposits. It does not explicitly name an alternative tool or state when not to use it, but the context is clear and precise.

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