Skip to main content
Glama

delete_proposal

Destructive

Delete a governance proposal on TRON by proposal ID; restricted to the proposal creator, a Super Representative.

Instructions

Delete a governance proposal (SR only, only the proposal creator can delete it).

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

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
proposalIdYesThe proposal ID to delete

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

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the description does not need to restate that the operation mutates state. It adds the key authorization context the annotations cannot convey — the caller must be a super representative and the proposal creator. It omits whether deletion is permanent or what happens to attached deposits/votes.

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 sentence with no filler; the resource is front-loaded and the permission caveats are compactly bracketed. The parenthetical packs two distinct constraints into one clause, but nothing is wasted.

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 destructive tool with full schema coverage, rich annotations, and no output schema, the description supplies purpose plus the critical permission gate. Remaining gaps (eligible proposal states, post-deletion effects) are secondary but real.

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 proposalId and network documented in the input schema, so the schema already carries parameter meaning. The description adds nothing about parameter handling or defaults, which is acceptable at this coverage level.

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 (delete a governance proposal) plus a scope qualifier, so an agent can distinguish it from approve_proposal, create_proposal, and get_proposal by name alone. It stops short of explicitly naming those siblings as alternatives, which keeps it from a 5.

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 gives the preconditions for legitimate use (SR only, creator only), which is useful gating information. It does not say when to prefer this over other governance actions or what proposal states are eligible, so guidance is implied rather than complete.

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