Skip to main content
Glama

Send a transaction (testnet, opt-in)

zenith_send

Send ZTH, ERC-20 tokens, or contract calls on Zenith testnet after a mandatory Gateway preflight and simulation. Blocked or unapproved sends are refused until you confirm.

Instructions

Sends ZTH, an ERC-20 transfer or a contract call on Zenith testnet. For a transfer to a Canton party, set gatewayPartyId (with token and amount): the full Gateway preflight runs first and blocked sends are refused. Plain sends to a Gateway inbox are refused so the checks cannot be skipped. Without confirm it only simulates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zenith_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRecipient or contract address
argsNo
tokenNoERC-20 to transfer (symbol or address)
amountNoToken amount (whole tokens)
confirmNoSet true only after the user approved the simulated plan
functionNoFunction signature for a contract call, e.g. "increment()"
valueZthNoNative ZTH to send, e.g. "0.1"
gatewayPartyIdNoSend to this Canton party through Gateway

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (non-readonly, open-world, non-idempotent), the description discloses that the full Gateway preflight runs automatically, that blocked sends are refused, and that omitting confirm only simulates. That is meaningful operational context for a mutation tool. It stops short of explaining what the simulation returns or how failures surface, which is a minor gap given no output schema.

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?

Four tight sentences, front-loaded with the send modes and then the Gateway-specific constraint and the confirm semantics. Density is high but nearly every clause carries a behavioral rule; the opening enumeration is slightly list-like but earns its place.

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?

For an 8-parameter, non-idempotent, open-world send tool with no output schema, the description covers the send modes, the Gateway path requirement, the preflight gate, and the simulate/confirm contract. What it lacks is any indication of network/token resolution or what a simulation response looks like, which would help an agent confirm success.

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 88%, so the baseline is 3, but the description adds cross-parameter semantics the schema cannot express: gatewayPartyId must be accompanied by token and amount, and confirm must only be set after the user approves the simulated plan. It doesn't clarify valueZth vs amount vs token interaction further, leaving one interrelation to the schema.

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 ('Sends ZTH, an ERC-20 transfer or a contract call on Zenith testnet') and enumerates the three send modes, which lets an agent map a request onto it immediately. It also distinguishes itself from the Gateway siblings by naming gatewayPartyId as the Gateway path rather than a separate tool.

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?

Gives concrete routing rules: use gatewayPartyId for Canton party transfers (paired with token and amount), and plain sends to a Gateway inbox are refused, which implicitly directs the agent to the Gateway flow. It also defines the simulation-first workflow via confirm. It does not name gateway_preflight or gateway_token_eligibility as prior steps, so the alternative-selection guidance is strong on the Gateway path but incomplete for pre-checks.

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