Skip to main content
Glama

Track a Gateway deposit

gateway_deposit_status
Read-only

Track a Zenith EVM-to-Canton deposit by transaction hash and get its current status plus the exact next step if held, evicted, mined, credited, or not a deposit.

Instructions

Follows a Zenith EVM → Canton deposit by transaction hash: held by Gateway (with reason and eviction time), evicted (with the nonce to resend at), mined and waiting for the inbox, credited (with the Gateway collection event), or not a deposit. Gives the exact next step from the docs' Common problems table.

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": {
      "hash": "<hash>"
    },
    "name": "gateway_deposit_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoSender address (helps when the transaction was evicted)
hashYesEVM transaction hash

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds substantial behavioral context by spelling out the possible outcome states, including that held deposits carry a reason and eviction time and evicted ones carry a nonce to resend. It does not describe latency, pagination, or how long a status remains valid, which keeps it below a 5.

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?

Front-loaded with the core action and scope, followed by the outcome taxonomy. The state enumeration is dense but each item carries decision-relevant detail; the only mild cost is that the list of states is packed into a single long sentence.

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?

With no output schema, the description carries the burden of explaining return values and does so comprehensively via the five outcome categories plus the 'exact next step' remediation. For a two-parameter read-only diagnostic tool, nothing an agent needs to interpret the result is missing.

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%, so both parameters are already documented. The description reinforces that lookup is by transaction hash but says nothing about the optional 'from' address, which the schema frames as helping with evicted transactions; it adds no meaning 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: it follows a Zenith EVM → Canton deposit keyed by transaction hash. The enumeration of terminal states (held, evicted, mined-pending-inbox, credited, not a deposit) makes it clearly distinct from a generic lookup like zenith_get_transaction.

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 usage context is clear: call this to diagnose where a cross-chain deposit is stuck, and it returns the next step. It stops short of naming alternatives (e.g. when to prefer zenith_get_transaction or gateway_inbox) or stating exclusions, so it does not reach a 5.

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