Skip to main content
Glama

get_proposal

Read-onlyIdempotent

Retrieve details of a specific TRON governance proposal by proposal ID, with optional network selection defaulting to mainnet.

Instructions

Get details of a specific governance proposal by its ID.

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": {
      "proposalId": "<proposalId>"
    },
    "name": "get_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
proposalIdYesThe proposal ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / proposalId / maximum
      Added value: +9007199254740991
  2. First observedv1.1.7

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is fully covered without the description. Beyond restating 'get details of a proposal', the description says nothing about what a proposal record contains, whether missing IDs error or return empty, or how the network selection affects results.

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?

A single efficient sentence with the key noun and lookup key front-loaded. It earns its brevity, though the brevity comes partly from omitting information rather than choosing tight wording over redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a lookup tool with no output schema, so the description is the only place to indicate what 'details' means and how a bad or missing proposalId behaves. It supplies neither, and the network parameter's effect on the result is also left unstated.

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 coverage is 100%, so both parameters — including the mainnet default on network — are already documented in the schema. The description's 'by its ID' adds no meaning beyond the proposalId definition, so the 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?

Specific verb ('Get') plus resource ('governance proposal') scoped to a single record by ID, which separates it from create_proposal, delete_proposal and approve_proposal. It stops short of naming any sibling explicitly, so it never explains the boundary between fetching one proposal and listing many.

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 or when-not-to-use guidance, no prerequisite context, and no mention of an alternative that returns proposal data. The phrase 'by its ID' only implies a valid existing proposalId is required, leaving the agent to infer the rest.

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