Skip to main content
Glama

create_proposal

Submit a TRON network governance proposal by mapping chain parameter IDs to proposed values; intended for Super Representatives.

Instructions

Create a new network governance proposal (SR only). Provide a map of chain parameter IDs to proposed values.

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": {
      "parameters": "<parameters>"
    },
    "name": "create_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
parametersYesMap of chain parameter key IDs (as string numbers) to proposed values. E.g. { '6': 100 } to propose changing parameter #6 to 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / parameters / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  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=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds the permission prerequisite (SR only), which is useful auth context, but says nothing about on-chain effects, fees, reversibility, or that the proposal still requires approval before taking effect.

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 action stated first and the required input second. Nothing would be lost by keeping it exactly as is.

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 mutation tool with rich annotations and full schema coverage, the essentials are present. The main omission is that, with no output schema, the description never hints at what is returned (a proposal ID or transaction hash) or that creation is only the first step in a multi-call flow.

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% and the parameters object already documents the string-keyed map with an example. The description merely restates that a map of parameter IDs to values is required and never mentions the optional 'network' parameter (mainnet default), which the schema covers on its own.

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?

The description opens with a specific verb and resource ('Create a new network governance proposal') and adds a meaningful qualifier ('SR only'), which separates it from approve_proposal and delete_proposal. It does not name siblings explicitly, so it falls just short of 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 '(SR only)' clause establishes a real prerequisite (caller must be a Super Representative), which is genuine usage guidance. However, there is no explicit statement of when to prefer this over approve_proposal/delete_proposal, and no note about what happens after creation (e.g. a subsequent approval step).

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