Skip to main content
Glama

Tokens Gateway can move

gateway_tokens
Read-only

Lists every token registered with Zenith Gateway with EVM and Canton details, transfer directions, and recipient requirements so you can plan cross-network transfers safely.

Instructions

Every token registered with Zenith Gateway, with both sides: EVM address, symbol and decimals; Canton instrument, symbol and scale; how each direction works and what the recipient needs (for example a standing acceptance for wrappers of Canton tokens).

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": "gateway_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful substance beyond that: it discloses the shape of the returned records and, with 'what the recipient needs (for example a standing acceptance for wrappers of Canton tokens)', surfaces a prerequisite the agent would otherwise miss. It still says nothing about volume, caching, or refresh behavior for a globally scoped catalog.

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 sentence, front-loaded with the scope ('Every token registered with Zenith Gateway'), that packs the return fields and the direction/recipient notes without filler. The semicolon-chained clauses make it dense to parse, but every clause carries information.

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 parameters and no output schema, the description carries the return-shape burden and does so by naming the fields on each side plus direction requirements. For a zero-arg read-only catalog, that is enough for an agent to call it confidently and interpret the result.

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?

The tool takes zero parameters, so there is no argument semantics to explain and the baseline of 4 applies. The description correctly signals the call needs no inputs by framing itself as an exhaustive 'every token' enumeration.

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 uses a specific verb-plus-resource pairing ('Every token registered with Zenith Gateway') and enumerates the returned fields on both sides (EVM address/symbol/decimals; Canton instrument/symbol/scale), so the agent knows this is a token catalog rather than a status or eligibility check. It never names a sibling, so routing against gateway_token_eligibility or gateway_deposit_status is left to inference.

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?

The 'every token registered' phrasing implies a discovery/reference lookup, but there is no explicit when-to-use or when-not-to-use, and no pointer to the eligibility or status siblings for follow-up checks. A reader can infer the use case but must supply the routing logic themselves.

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