Skip to main content
Glama

Deposit USDG into the shielded balance

deposit

Moves USDG from the agent wallet into a shielded balance as a new note, sending approve and funding transactions and waiting for confirmation so the note can pay orders after clean-funds approval.

Instructions

Moves USDG from the agent's deposit wallet (see get_balance) into its shielded balance as a new note. The deposit itself is public: anyone can see this wallet deposited this amount; what the note pays for later is not linked to it. Sends two transactions (approve, deposit) and waits for them. The new note can pay for orders once the clean-funds check approves it, usually within a minute. Up to 1,000 USDG per deposit until the audit.

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

Input Schema

NameRequiredDescriptionDefault
usdgAmountYesUSDG to deposit (1 to 1,000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does well: it discloses that the deposit is public while the later spend is unlinked, that two transactions (approve, deposit) are sent and awaited, the clean-funds approval latency, and a temporary 1,000 USDG cap. What remains undisclosed is the return value (transaction hashes or note id), failure/revert behavior, and gas/signing requirements, which matters for an unannotated mutation tool.

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?

Four tight sentences, front-loaded with the core action, then privacy implication, then mechanics, then limits. No sentence is filler and each adds a distinct operational fact.

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?

For a single-parameter, output-schema-less mutation tool with no annotations, it covers privacy model, transaction sequencing and blocking behavior, timing, and limits. The notable remaining gap is what the call returns on success and how failures surface, which an agent needs to verify the deposit landed.

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% and the schema already documents the 1 to 1,000 range, so the baseline is 3; the description adds that the cap is temporary ("until the audit") and reinforces the amount's role as the deposit size, which is modest but real added meaning.

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 ("Moves USDG from the agent's deposit wallet ... into its shielded balance as a new note") and explicitly points to get_balance, so the agent can separate it from the sibling wallet/order tools without opening a 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?

Explains the pre-condition implicitly by naming get_balance for the source wallet, and gives the follow-on usage rule: the resulting note can pay for orders only after the clean-funds check, usually within a minute. It states no explicit when-not-to-use or alternative deposit path, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.