Skip to main content
Glama

convert_address

Read-onlyIdempotent

Convert TRON addresses between Hex and Base58 formats by supplying an address string, enabling compatibility across wallets, tools, and APIs.

Instructions

Convert addresses between Hex and Base58 formats

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

Input Schema

NameRequiredDescriptionDefault
addressYesAddress to convert (Hex or Base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only that the conversion is bidirectional, and says nothing about how the source format is detected or what happens if the input is neither Hex nor Base58 — meaningful gaps even at the lower bar annotations set.

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?

One sentence, front-loaded with the verb and the two formats, with no filler. It is efficient but so terse that it omits useful qualifiers rather than being fully optimized.

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?

This is a simple, single-parameter, non-destructive tool whose annotations carry the safety information, so the bar is low. Still, with no output schema, the description never indicates what comes back (a single converted string? both forms?) or how failure is surfaced, leaving the agent to guess at the result shape.

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?

There is a single parameter at 100% schema coverage, and the schema already states the address may be Hex or Base58. The description adds no syntax, length, prefix, or case-handling detail beyond that, so the baseline 3 applies.

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?

Names a specific verb ('Convert') and resource ('addresses') plus the two formats involved, so the operation is unambiguous. It does not explicitly distinguish itself from nearby siblings like validate_address or get_wallet_address, which is the only reason it falls short of a 5.

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 format-conversion framing implicitly tells an agent when this applies, but there is no explicit statement of when to use it instead of validate_address or get_wallet_address, and no mention of error behavior for an unparseable input.

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

Deploy Server

Other Tools