Skip to main content
Glama

vote_witness

Cast votes for TRON Super Representatives using TRON Power earned by freezing TRX; each frozen TRX provides one vote.

Instructions

Vote for Super Representatives using TRON Power (obtained by freezing TRX). Each frozen TRX = 1 vote.

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": {
      "votes": "<votes>"
    },
    "name": "vote_witness"
  }
}

Input Schema

NameRequiredDescriptionDefault
votesYesList of SR addresses and vote counts
networkNoNetwork name. Defaults to mainnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / votes / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / votes / items / properties / voteCount / maximum
      Added value: +9007199254740991
  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?

The annotations already disclose that this is a non-read-only, open-world, non-idempotent operation, so the description carries a lighter burden. It adds useful context about the frozen-TRX-to-vote conversion, but it omits transaction lifecycle details such as fees, confirmation, or whether votes can be changed later.

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?

The definition is two compact sentences with no filler, and the core action is front-loaded. The prerequisite and conversion rule are stated efficiently without redundant restatement of the tool name.

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

Completeness3/5

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

For a non-idempotent, open-world write operation with no output schema, the description covers the purpose and vote-power prerequisite. It remains thin on broadcast/signing expectations, fees, and whether existing votes can be reallocated or revoked.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by tying vote allocation to TRON Power obtained from frozen TRX. It does not explain the optional network parameter, but that is already documented in the schema.

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 states a specific verb and resource: voting for Super Representatives using TRON Power. It is clear enough to distinguish from witness-creation or witness-update tools, but it does not explicitly name those siblings or state when it is not appropriate.

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 description gives an important precondition: TRON Power must be obtained by freezing TRX. However, it does not explicitly say when to use this tool versus adjacent operations such as create_witness or update_witness, nor does it describe exclusions or post-vote behavior.

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