Skip to main content
Glama

Mailbox party for Canton → EVM

gateway_mailbox
Read-only

Derives the Canton transfer destination party for an EVM address and token, reports whether it is absent, requested, or active, and explains how to request it.

Instructions

Derives the mailbox party for an EVM address and token (the Canton party you transfer to, to move that token to that EVM address) and reports its state: absent, requested, active and so on. Explains how to request it.

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": {
      "evmAddress": "<evmAddress>",
      "token": "<token>"
    },
    "name": "gateway_mailbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesToken: "ZTH", a symbol (e.g. DevUSD, DORIG), a Canton instrument ID or an ERC-20 address
evmAddressYesDestination EVM address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 value by disclosing the returned state vocabulary (absent, requested, active) in the absence of an output schema. It also mentions it explains how to request the party, orienting the agent toward the follow-up action. A minor gap: it doesn't say this call itself creates nothing.

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?

Two sentences, front-loaded with the core action and followed by a clarifying summary of states and the request path. Nothing is redundant and the parenthetical earns its place by defining 'mailbox party'.

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?

With no output schema, the description does the work of telling the agent what comes back (a state among absent/requested/active) and that a request step exists. Only the mechanics of 'how to request' are left unstated, which is acceptable for a two-parameter read tool.

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 token and evmAddress formats are already fully documented in the schema. The description adds intent (destination EVM address, which token to move) but no format, enum, or edge-case detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: derives the mailbox party for an EVM address plus token and reports its state. The parenthetical clarifies the business meaning (the Canton party you transfer to). It does not name a sibling to differentiate against, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the parenthetical: use this to find the destination party before moving a token to an EVM address. There is no explicit when-not guidance and no named alternative (e.g. a preflight or deposit-status sibling) for the case where the party is already active or where the transfer path differs.

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