Skip to main content
Glama

deposit

Read-only

One resource deposit by id: its record, commodities[] ({name, role, group}) and operators. Pair with deposits(commodity=…) to find ids. Metered: see CHARGING in the server instructions; quote first with billing_quote.

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": {
      "id": "<id>"
    },
    "name": "deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe deposit's numeric id (from `deposits`, a pin, or a relationship row).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / id / title
      Removed value: -"Id"
    • removedInput schema / title
      Removed value: -"depositArguments"
    • removedOutput schema / title
      Removed value: -"depositDictOutput"
  2. Changed2 schema fields changed
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "integer"
      +  }
      +]
    • removedInput schema / properties / id / type
      Removed value: -"string"
  3. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"The deposit's numeric id (from `deposits`, a pin, or a relationship row)."
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/closed-world, and the description adds genuinely new behavioral context: the call is metered and should be quoted before use via `billing_quote`. It stops short of saying what happens for an unknown id (error vs empty), which is the only notable gap for a lookup.

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 clauses of roughly equal value, front-loaded with what the tool returns. The density of backticked tool names is slightly heavy but every sentence carries actionable 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?

A single-parameter read with an output schema, so return shape needs little prose; the description covers sourcing the id and the cost gate. The only missing piece is failure behavior for a nonexistent id, which is minor given the output schema and read-only annotations.

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 coverage is 100% and the `id` property already documents its type flexibility and provenance (from `deposits`, a pin, or a relationship row). The description only reinforces where ids come from, adding no format or validation detail beyond the schema, so baseline 3 applies.

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 (fetch one deposit by id) and enumerates the payload (record, commodities[] with {name, role, group}, operators). It also explicitly contrasts itself with the sibling `deposits`, so an agent can distinguish a single-record lookup from the list/search tool without opening either schema.

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?

Gives an explicit recipe: use `deposits(commodity=…)` to obtain ids, then call this tool, and quote cost first with `billing_quote`. It does not mention when to prefer the nearby sibling `deposit_brief`, which is the main remaining routing ambiguity.

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