Skip to main content
Glama

validate_address

Read-onlyIdempotent

Verifies a TRON address and identifies its format (Base58 or Hex), helping prevent errors before transactions or contract interactions.

Instructions

Validate a TRON address and detect its format (Base58 or Hex).

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

Input Schema

NameRequiredDescriptionDefault
addressYesAddress to validate

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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without description help. The description adds the useful behavioral fact that the tool also classifies the address format, but it says nothing about what happens on an invalid input (error, false, or failure object), which matters for a validator.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with no filler, front-loading the primary action and appending the secondary output in parentheses. Nothing is wasted and nothing is buried.

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?

There is no output schema, so the description is the only place an agent can learn what a successful call returns (a boolean, a format label, or both) or how failure is signaled. Given the tool's simplicity the gap is small, but for a validator specifically the return contract is the missing piece.

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 description coverage is 100% for the single 'address' parameter, so the baseline is 3 and the schema carries the burden. The description adds nothing about accepted forms — whether hex input needs a 0x prefix, whether whitespace or checksum issues are tolerated — despite format detection being the tool's stated second job.

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?

States a specific verb and resource ('Validate a TRON address') and adds a secondary function ('detect its format (Base58 or Hex)'), which is enough to separate it from conversion-oriented siblings like convert_address. It does not explicitly name or rule out those siblings, so it stops 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 Guidelines2/5

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

The description contains no when-to-use or when-not-to-use guidance; it never mentions that convert_address exists for transforming addresses rather than checking them. An agent can infer the validation purpose from the verb, but nothing in the text routes it between this tool and its alternatives.

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