Skip to main content
Glama

Canton party → inbox address

gateway_inbox
Read-only

Validates a full Canton party ID, rejects invalid or protocol parties, then computes its EVM inbox address and checks deployment and registry status.

Instructions

Checks a Canton party ID and computes its inbox: the EVM address that delivers to that party on Canton. Rejects shortened IDs, protocol parties (m-, r-, b-) and the Gateway party, says whether the inbox is deployed, and cross-checks the registry API.

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": {
      "partyId": "<partyId>"
    },
    "name": "gateway_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
partyIdYesFull Canton party ID: hint::1220 followed by 64 hex digits

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 establish readOnlyHint=true and openWorldHint=true, so the burden is lower, and the description still adds real behavior: it enumerates the rejection classes (shortened IDs, protocol parties m-/r-/b-, the Gateway party), reports deployment status, and discloses an external registry API call. It omits what happens on a rejected ID (error vs. negative result), which is the main remaining gap.

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?

A single dense sentence with the core action front-loaded before the validation and side-effect clauses. Nothing is padding, though the colon-list construction makes it slightly denser than ideal for scanning.

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 one required parameter, no output schema, and annotations covering the safety profile, the description covers the input, the failure modes, and a partial picture of the return (deployed status). It stops short of describing the full result shape, which matters somewhat given there is no output schema.

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 format (hint::1220 plus 64 hex digits) is already documented. The description nonetheless adds semantics the schema lacks: which classes of syntactically valid party IDs are still rejected, which meaningfully changes what the agent should pass.

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?

The description names a concrete verb pair (checks/computes) and a concrete resource (the inbox EVM address for a Canton party), plus the derived value it returns. That is far more specific than the title alone. It does not, however, distinguish itself from near-name siblings such as gateway_mailbox, so an agent must infer the split.

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 validation rules: use this before delivering to a party, since it rejects malformed or ineligible party IDs. There is no explicit "use this instead of X" statement and no stated precondition about when the registry cross-check matters.

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