Skip to main content
Glama

get_contract_info

Read-onlyIdempotent

Retrieve a TRON contract's ABI, readable function signatures, and raw metadata by contract address to inspect or integrate with smart contracts.

Instructions

Get high-level information about a contract: ABI, readable function signatures, and raw metadata.

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

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

B3.4/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=true, so the safety profile is covered. The description contributes the content of the read (ABI, signatures, metadata) but says nothing about response size for large ABIs, rate limits, or behavior on an unverified/nonexistent contract.

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?

A single front-loaded sentence with a colon-delimited payload list and no filler. Every clause adds information about what the tool returns.

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?

With only two well-described parameters, full annotations, and no output schema, the definition is nearly self-sufficient; the description usefully previews the returned fields in place of an output schema. The remaining gap is routing guidance against the many contract-related siblings, which is not addressed.

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% and both parameters (contractAddress, network) are documented in the schema itself, including the mainnet default. The description adds no format hints such as address encoding or network naming conventions, so it sits at the baseline of 3.

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 and resource ('Get high-level information about a contract') and enumerates the payload (ABI, readable function signatures, raw metadata), so the agent knows exactly what comes back. It does not, however, distinguish itself from plausible siblings such as get_contract or fetch_contract_abi, leaving overlap ambiguous.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance at all. The agent must infer from the returned fields that this is for reading a contract's ABI/metadata, and must guess how it differs from the ABI-fetching and contract-reading siblings.

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