Skip to main content
Glama

sign_message

Idempotent

Signs arbitrary messages with the configured TRON wallet so AI agents can prove wallet ownership or authenticate blockchain actions.

Instructions

Sign an arbitrary message using the configured wallet.

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": {
      "message": "<message>"
    },
    "name": "sign_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe message to sign

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description contributes that signing uses a pre-configured wallet (no key parameter, no key material handled by the caller), but says nothing about whether the wallet must be unlocked, whether signing has side effects, or what form the signature takes.

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?

One front-loaded sentence with no filler; the operation and the signing key source come first. It is efficient but borders on under-specified rather than fully earning its brevity.

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 one-parameter tool with no output schema, the description is nearly adequate, but it never indicates what is returned (raw signature hex, base64, object) or what encoding the message input expects. Those gaps matter for a signing primitive an agent will chain into broadcast steps.

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?

With 100% schema coverage and a single required parameter already documented, the schema does the heavy lifting. The description adds only the implication that the message is unconstrained free-form text rather than a structured payload, which is marginal value.

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 ("Sign an arbitrary message") plus the key source ("configured wallet"), which is more informative than the bare name. It does not distinguish itself from neighboring write-path tools like create_transaction or broadcast_transaction, so an agent must infer that signing is a separate step from broadcasting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus creating or broadcasting a transaction, nor on prerequisites such as an unlocked or configured wallet. The word "arbitrary" hints at off-chain or non-transaction payloads but never states the boundary explicitly.

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