Skip to main content
Glama

update_witness

Updates the official website URL for a configured TRON Super Representative node; the wallet must already hold SR status.

Instructions

Update the SR node website URL for the configured wallet (must already be an SR).

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe new official website URL for the SR
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds the useful precondition that the wallet must already be an SR, but says nothing about broadcast behavior, error on non-SR, or whether the change is immediately on-chain.

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 front-loaded sentence with the resource and the key precondition; no wasted wording. Slightly terse given the mutation's implications.

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?

Adequate for a simple two-parameter mutation: parameters, safety hints, and precondition are all present. It omits what happens on failure (wallet not an SR) and what the call returns, which matters somewhat for a non-idempotent write.

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% with both url and network documented, so baseline is 3. The description clarifies that url is the SR's official website URL, but adds no format or network-selection detail beyond 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?

Specific verb (update) and resource (SR node website URL), plus a scope constraint (configured wallet, already an SR). It is distinguishable from create_witness and vote_witness, though it does not name alternatives explicitly.

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?

States a precondition (the wallet must already be an SR) and implies the operation targets the configured wallet, which helps selection. But there is no explicit when-to-use/when-not guidance or pointer to related tools like create_witness for non-SR cases.

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