Skip to main content
Glama

iota_wallet_address

Retrieve the active wallet address for IOTA blockchain interactions, enabling AI agents to manage wallets and execute transactions securely.

Instructions

Get the active wallet address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration for iota_wallet_address calling the wallet helper.
    server.tool(
      "iota_wallet_address",
      "Get the active wallet address",
      {},
      async () => text(await wallet("/address"))
    );
  • The wallet helper function which communicates with the local wallet server.
    async function wallet(path: string, method = "GET", body?: unknown): Promise<string> {
      try {
        const opts: RequestInit = {
          method,
          headers: { "Content-Type": "application/json" },
        };
        if (body) opts.body = JSON.stringify(body);
        const res = await fetch(`${WALLET_SERVER}${path}`, opts);
        if (!res.ok) return `Wallet server error ${res.status}: ${res.statusText}`;
        return await res.text();
      } catch (err: any) {
        return `Wallet server unreachable (${WALLET_SERVER}): ${err.message}. Start the agent-wallet server first.`;
      }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it's a 'Get' operation, implying read-only behavior, but doesn't disclose any behavioral traits such as authentication requirements, rate limits, or what 'active' means in context (e.g., default, currently selected).

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 a single, efficient sentence with no wasted words. It's front-loaded and appropriately sized for a simple tool with no parameters.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate. However, it lacks context about what 'active' means and doesn't explain the return value, leaving gaps for an AI agent to understand the full behavior.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but with no parameters, the baseline is 4 as it's complete in this aspect.

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 'Get the active wallet address' clearly states the action (Get) and resource (active wallet address). It's specific but doesn't differentiate from sibling tools like 'iota_wallet_accounts' or 'iota_wallet_balance' that might also retrieve wallet information.

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?

No guidance is provided on when to use this tool versus alternatives. With sibling tools like 'iota_wallet_accounts' (plural) and 'iota_wallet_balance', the description doesn't clarify if this retrieves a single default address versus multiple addresses or balance information.

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/Scottcjn/iota-agent-mcp'

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