Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

address_decode

Read-only

Convert a bech32m Chia address (xch1 or txch1) back to its puzzle hash locally without RPC. Flags cross-network prefix mismatches so you can verify the address before running on-chain queries.

Instructions

Decode a bech32m Chia address (xch1... or txch1...) back to its puzzle hash. Pure local computation, no RPC call. If the address prefix doesn't match the configured network (e.g., decoding a txch1... address on mainnet), the result includes a warning field — cross-network decoding is allowed but may indicate the address belongs to a different network. Always check the warning field before using the puzzle hash for on-chain queries.

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": {
      "address": "<address>"
    },
    "name": "address_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe bech32m Chia address to decode (xch1... or txch1...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does so well: it discloses the no-RPC local execution model, the existence of a 'warning' field, the exact condition that triggers it (prefix/configured-network mismatch), and that mismatches are tolerated rather than rejected. That is return-value behavior an agent could not infer from annotations or 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?

Three sentences, front-loaded with the core operation before the caveat and the call to action. Mild redundancy between the parenthetical example and the clause 'cross-network decoding is allowed but may indicate the address belongs to a different network' — the same point is made twice — but nothing is seriously wasteful.

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?

For a one-parameter, side-effect-free decode tool with no output schema, the description covers the input format, execution model, the one non-obvious return field, and the required follow-up check. An agent has everything needed to call it and interpret the result correctly.

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% and the single 'address' parameter is already documented with the same xch1.../txch1... examples, so most of the description's parameter text repeats the schema. It does add meaning by tying the address prefix to the configured network and explaining the consequence of a mismatch, but that is framed as output behavior more than parameter semantics.

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 and resource — 'Decode a bech32m Chia address ... back to its puzzle hash' — and names the accepted prefix formats (xch1.../txch1...). The word 'decode' and the direction 'back to its puzzle hash' inherently distinguish it from the inverse sibling address_encode without needing to name it.

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 clear context for use: it is a pure local computation with no RPC call, and the resulting puzzle hash feeds on-chain queries. It also states that cross-network decoding is permitted rather than blocked, which tells the agent the tool will not fail on a mismatch. It does not explicitly name address_encode or any alternative, so no true exclusion guidance is present.

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