Skip to main content
Glama

ledger_verify_address

Read-only

Display an address on your Ledger device for physical verification to confirm its accuracy before use.

Instructions

Display address on Ledger device for physical verification

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for ledger_verify_address tool. Checks signer, validates ledger key type, calls ledgerShowAddress with timeout, returns verification result.
    registry.register({
      name: 'ledger_verify_address',
      group: 'ledger',
      description: 'Display address on Ledger device for physical verification',
      schema: {},
      annotations: { readOnlyHint: true },
      handler: async (_params, { chainManager, config }) => {
        chainManager.requireSigner();
    
        if (config.key.type !== 'ledger') {
          return success({ verified: false, reason: 'Not using Ledger key.' });
        }
    
        const address = await Promise.race([
          chainManager.ledgerShowAddress(),
          new Promise<never>((_, reject) =>
            setTimeout(
              () => reject(new LedgerSignError('Address verification timed out.')),
              LEDGER_SIGN_TIMEOUT,
            ),
          ),
        ]);
    
        return success({ verified: true, address });
      },
    });
  • No input schema required for ledger_verify_address (empty object).
    schema: {},
  • Registration of ledger_verify_address tool in the singleton ToolRegistry via registry.register().
    registry.register({
      name: 'ledger_verify_address',
      group: 'ledger',
      description: 'Display address on Ledger device for physical verification',
      schema: {},
      annotations: { readOnlyHint: true },
      handler: async (_params, { chainManager, config }) => {
        chainManager.requireSigner();
    
        if (config.key.type !== 'ledger') {
          return success({ verified: false, reason: 'Not using Ledger key.' });
        }
    
        const address = await Promise.race([
          chainManager.ledgerShowAddress(),
          new Promise<never>((_, reject) =>
            setTimeout(
              () => reject(new LedgerSignError('Address verification timed out.')),
              LEDGER_SIGN_TIMEOUT,
            ),
          ),
        ]);
    
        return success({ verified: true, address });
      },
    });
  • ChainManager.ledgerShowAddress() - Helper that dynamically imports @initia/ledger-key, validates the key is a LedgerKey, calls showAddressAndPubKey() on the ledger device, and returns the address.
    async ledgerShowAddress(): Promise<string> {
      if (!this.key) throw new SignerRequiredError();
      const { LedgerKey } = await import('@initia/ledger-key');
      if (!(this.key instanceof LedgerKey)) {
        throw new LedgerConnectionError('Key is not a LedgerKey instance.');
      }
      const lk = this.key as any;
      await lk.showAddressAndPubKey();
      return this.key.address;
    }
Behavior4/5

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

Annotations already mark the tool as read-only. The description adds context about the physical verification step on the device, which is not captured by annotations. No contradictions.

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?

Single concise sentence that front-loads the key action and purpose. No extraneous content.

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 parameterless tool with a straightforward action, the description is nearly complete. Minor omission: does not mention that a Ledger must be connected.

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?

Input schema has zero parameters, so description naturally covers parameter semantics. No need for additional details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies a concrete action ('Display address on Ledger device') and the purpose ('physical verification'), clearly distinguishing it from siblings like 'address_validate' or 'ledger_status'.

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 implies its use case (physical verification on a Ledger device) but does not explicitly state when to prefer this over alternatives or mention any prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/initia-labs/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server