Geode

Send GEODE

geode_balances_transfer

Destructive

Send GEODE from signer to another account (keep-alive transfer: your account can never be emptied below the minimum balance). Irreversible, so the first call returns a confirm_token and the real cost; call again with it to get the intent. Sign with geode-local-signer, restating the recipient and amount in expect, then submit with geode_submit_intent. Sending to a new address creates that account (at least 1 GEODE). Counts toward the per-transaction and rolling 24-hour caps.

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": {
      "signer": "<signer>",
      "dest": "<dest>",
      "amount": "<amount>"
    },
    "name": "geode_balances_transfer"
  }
}

Input Schema

Name	Required	Description
`dest`	Yes	Recipient account address (SS58)
`amount`	Yes	Amount in GEODE as a decimal string (e.g. "1.25"), or {"raw": "<planck>"}
`signer`	Yes	Your account address (SS58). The transaction is prepared for this account; you sign it on your own machine with geode-local-signer.
`confirm_token`	No	Token from the first call

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already flag destructive/openWorld/not-readOnly, but the description adds substantially more: irreversible, keep-alive so the account can never be emptied below minimum balance, two-phase confirmation with a confirm_token, account creation on send to a new address, and rate-cap exposure.

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 and every clause carries operational meaning; there is little filler. The single dense paragraph packs the two-step flow, signing step, and caps into one wall of text, which slightly hurts scanability.

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 correctly explains what the first call returns (confirm_token and real cost) and what to do next, plus constraints. It does not cover confirm_token expiry or mismatch behavior, which matters for an irreversible transfer, but the core flow is adequately documented.

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 the schema already documents signer, dest, amount, and confirm_token; the description adds lifecycle context for confirm_token (returned by first call, reused on second). However, it introduces '`expect`' — a field of geode-local-signer, not of this tool's schema — which could mislead an agent into passing an unsupported parameter.

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 precise verb+resource: 'Send GEODE from `signer` to another account', and immediately qualifies it with keep-alive semantics. It is clearly distinguishable from siblings such as geode_submit_intent, which it names as the final step rather than a competitor.

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

Usage Guidelines5/5

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

Lays out the exact operating procedure: first call returns confirm_token and real cost, second call retrieves the intent, sign with geode-local-signer, then submit with geode_submit_intent. It also states the new-address minimum (1 GEODE) and that this counts toward per-transaction and 24-hour caps.

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

All Geode tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?