Skip to main content
Glama

get_approved_list

Read-onlyIdempotent

Retrieves the list of accounts that signed a given TRON transaction by submitting the full transaction JSON.

Instructions

Query the list of accounts that have signed a given transaction. Pass the full transaction JSON object.

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": {
      "transaction": "<transaction>"
    },
    "name": "get_approved_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
transactionYesThe full signed transaction as a JSON string

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and network-access profile is covered. The description adds only that it operates on a signed transaction, without saying whether unsigned input errors out or how many signers are needed. With annotations carrying the behavioral burden, this is adequate but thin.

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 core action front-loaded and the invocation note second. Nothing in it is redundant enough to cut.

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-only lookup with full schema coverage and annotations, the description covers what is queried and how to supply input. It does not mention the return shape (account identifiers/addresses) or behavior on invalid or unsigned transactions, which would complete it, but there is no output schema to compensate.

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%, so both parameters, including the mainnet default for network, are already documented. The description's emphasis on passing the 'full' transaction reinforces that partial JSON is insufficient, a marginal addition beyond the schema's own wording.

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: queries the list of accounts that signed a given transaction. That is clearly distinct from the sibling get_account*/list_* tools, which deal with accounts, blocks, or contracts rather than transaction signers. It stops short of naming a sibling it might be confused with, but the resource 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 second sentence ('Pass the full transaction JSON object') is a calling instruction, not a when-to-use rule. There is no guidance on when this is preferred over related lookups or on any prerequisites such as the transaction already being signed. Usage is only implied by the resource name.

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