Skip to main content
Glama

Report a deposit transaction

report_deposit
Idempotent

Submits the source-chain deposit transaction hash for an existing swap so the router detects it immediately instead of waiting for the next scan; it never moves funds.

Instructions

Tell the router the hash of the deposit transaction the user just sent, so the swap is detected immediately instead of on the next scan. Optional: swaps are detected without it, and it never moves funds. swap_id is the id create_swap returned for this swap. tx_hash is the hash of the transaction that sent funds to that swap's deposit_address on the source chain (0x-prefixed on EVM chains); never pass a payout hash or another swap's id. An unknown swap_id returns an error. Use it once, right after the user shares their tx hash, then follow up with get_swap_status. Calling it again with the same hash is harmless.

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": {
      "swap_id": "<swap_id>",
      "tx_hash": "<tx_hash>"
    },
    "name": "report_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
swap_idYesswap_id returned by create_swap.
tx_hashYesHash of the user's deposit transaction on the source chain (0x... on EVM chains). Letters and digits only, up to 128 characters.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the router accepted the hash.
next_stepNoWhat to do next.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, yet the description adds genuinely new behavior: unknown swap_id yields an error, swaps are detected without this call (it is an accelerator, not a requirement), and it never moves funds — which usefully resolves the tension with readOnlyHint=false. It stops short of covering auth/prerequisites or failure modes beyond the unknown-id case.

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?

Purpose and benefit are front-loaded in the first sentence, then optionality, then parameter disambiguation, then the call sequence. Every sentence carries distinct information — the only mild redundancy is the harmless-repeat clause, which still adds reassurance.

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?

An output schema exists, so return shape need not be described, and the annotations carry the safety profile. The description still covers error behavior, idempotency, optionality, and the follow-up step, leaving nothing an agent needs in order to call it correctly.

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 the baseline is 3, but the description adds real meaning beyond it: tx_hash must be the deposit tx that sent funds to that swap's deposit_address on the source chain, and explicitly must not be a payout hash or another swap's id. That negative guidance targets the most likely agent mistake.

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 — telling the router the deposit tx hash so the swap is detected immediately — and pins its effect (faster detection, not fund movement). It is clearly distinguishable from create_swap (which returns swap_id) and get_swap_status (the follow-up read).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly marks the call optional ('swaps are detected without it'), gives the trigger ('right after the user shares their tx hash'), the frequency ('use it once'), and names the next step ('follow up with get_swap_status'). When-to-use, when-not-to-use, and the alternative path are all covered.

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