Skip to main content
Glama

Convert amounts between Zenith EVM and Canton

gateway_convert
Read-only

Converts Gateway token amounts between EVM and Canton using the correct crossing rules, ensuring exact results without silent rounding.

Instructions

Exact amount conversion for a Gateway token, in either direction, with the crossing rules applied: one EVM base unit is 1e-10 on Canton, 18-decimal tokens show 10^8 times larger on Canton (DORIGe-8), ZTH crosses in multiples of 10^8 wei and wZTH back in whole gwei. Never rounds silently.

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": {
      "token": "<token>",
      "direction": "<direction>",
      "amount": "<amount>"
    },
    "name": "gateway_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoFor to-canton: whole tokens or EVM base unitstoken
tokenYesToken: "ZTH", a symbol (e.g. DevUSD, DORIG), a Canton instrument ID or an ERC-20 address
amountYes
directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description correctly focuses on behavior: exactness, the EVM-to-Canton base-unit ratio, the DORIGe-8 scaling, and the ZTH/wZTH multiple constraints. "Never rounds silently" signals a precision guarantee, though it leaves open whether a non-crossable amount errors out or is rejected in another way.

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?

Purpose is front-loaded in the first clause, and every subsequent clause adds a concrete rule rather than filler. The dense ratio list (1e-10, 10^8, DORIGe-8, gwei) is information-rich but harder to parse than a broken-out structure would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter read-only tool with no output schema, the description covers the numeric rules but omits what the call returns (a converted amount string, presumably, and in which unit) and what happens when an amount violates the crossing multiple. Those are the two facts an agent most needs before relying on the result.

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 50%: unit and token are documented in the schema, while amount and direction are not. The description compensates somewhat by stating that conversion works "in either direction" and by giving validity constraints on amounts (multiples of 10^8 wei, whole gwei), but it does not clarify the string format of amount or how unit interacts with direction beyond what the schema already says.

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 specific verb and resource ("Exact amount conversion for a Gateway token, in either direction") and scopes it to cross-chain amount math, which no sibling tool appears to do. It stops short of explicitly contrasting itself with neighboring tools such as gateway_preflight or gateway_tokens, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or exclusions. An agent must infer that this is for computing cross-chain amounts, and nothing tells it whether to call this before a deposit or how it relates to gateway_preflight or gateway_token_eligibility.

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