Skip to main content
Glama

create_witness

Destructive

Apply to become a TRON Super Representative (SR) by submitting your official website URL. Uses the configured wallet and burns 9999 TRX as the application fee.

Instructions

Apply to become a Super Representative (SR). Requires the configured wallet and burns 9999 TRX as application fee.

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": {
      "url": "<url>"
    },
    "name": "create_witness"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe official website URL of the SR candidate
networkNoNetwork name. Defaults to mainnet.

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.8/5.0
Behavior4/5

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

Annotations already declare this as non-read-only, destructive, and non-idempotent. The description adds meaningful context beyond that by stating the wallet prerequisite and the exact 9999 TRX application fee, which are important operational details for an agent.

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 description is two tight sentences with no wasted wording. It front-loads the purpose and follows with the most important prerequisite and cost.

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 destructive create/application tool, the description covers the action, wallet requirement, and fee, while annotations cover the safety profile. Remaining details such as the URL's use and network default are already documented in the schema, so no critical gap remains.

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 the schema already defines both the required website URL and the optional network parameter. The description adds no additional parameter-level semantics beyond what the schema provides, making the baseline score appropriate.

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 clear action and resource: applying to become a Super Representative. It distinguishes the application step from update_witness or vote_witness by wording, but it does not explicitly name sibling tools or contrast their use cases.

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 prerequisite of a configured wallet and the 9999 TRX fee imply when the tool is applicable, but there is no explicit guidance on when to use it versus update_witness, vote_witness, or other creation tools. The context is clear enough for a candidate action, but alternative routing is absent.

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