Skip to main content
Glama

clear_abi

Destructive

Clears a contract's on-chain ABI metadata using the creator's wallet, removing ABI data from the specified TRON contract address on the chosen network.

Instructions

Clear the on-chain ABI metadata of a contract (ClearABIContract). Requires the contract creator's wallet.

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

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
contractAddressYesThe contract address whose ABI will be cleared

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

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

Annotations already flag destructiveHint=true, readOnlyHint=false and openWorldHint=true; the description adds what exactly is destroyed (the on-chain ABI metadata) and the auth constraint (creator's wallet). It does not mention cost/energy, irreversibility, or that clearing twice is flagged non-idempotent.

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 front-loaded sentence with the destructive action first and the prerequisite second; no wasted prose. The parenthetical ClearABIContract is marginally redundant but aids traceability to the chain operation.

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 simple 2-parameter, no-output-schema tool with rich annotations, the description covers the action, its target, and the key auth requirement. Minor gaps — expected energy/fee, permanence of the clear, and post-clear effect on verified interfaces — would round it out.

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%, with both network (defaults to mainnet) and contractAddress documented in the schema itself. The description adds no parameter-level meaning beyond that, so 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?

States a specific verb and resource: clearing on-chain ABI metadata for a contract, and names the underlying operation ClearABIContract. It implicitly contrasts with the sibling fetch_contract_abi (read vs. clear), though it never names that alternative explicitly.

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?

Gives one real precondition — the contract creator's wallet must be used — which is useful context for selecting this tool. It does not say when to use this instead of related operations (e.g., fetching ABI, redeploying, or updating a contract), so routing guidance is only implied.

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