Skip to main content
Glama

fetch_contract_abi

Read-onlyIdempotent

Fetches the ABI entry array for a verified TRON contract address, giving AI agents the interface needed to interact with smart contract functions.

Instructions

Fetch contract ABI from the chain (for verified contracts). Returns the ABI entry array.

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": {
      "contractAddress": "<contractAddress>"
    },
    "name": "fetch_contract_abi"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
contractAddressYesThe contract address

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

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false) and open-world access, so the bar is lower. The description adds real value with the verified-contract restriction and the return shape ('ABI entry array'), but it says nothing about failure behavior for unverified or non-existent contracts, which is the main behavioral unknown here.

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?

Two short sentences, zero filler, with the scope qualifier and return value front-loaded. Nothing needs to be trimmed.

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?

For a two-parameter read tool with full schema coverage and rich annotations, the definition covers purpose, precondition, and return shape. The only meaningful gap is error behavior for unverified contracts, which the agent may need to interpret a failed call.

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 both parameters, including the network default to mainnet, so the schema already carries parameter meaning. The description adds nothing about contractAddress format or valid network names beyond that. Baseline 3 applies when the schema does the heavy lifting.

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 ('Fetch contract ABI'), names the source ('from the chain'), and scopes it with the parenthetical '(for verified contracts)'. It also states the return shape. It stops short of distinguishing itself from nearby siblings like read_contract or get_contract_info, but the operation itself is unambiguous.

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 parenthetical '(for verified contracts)' implies a precondition and therefore an implicit when-to-use rule, but the description never says what to do for unverified contracts or points to an alternative tool when this one is not applicable. Usage is implied rather than stated.

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