Skip to main content
Glama

get-account

Retrieve the currently active MetaMask wallet address to enable blockchain interactions and transaction signing while keeping private keys secure in your wallet.

Instructions

Get the current account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic: retrieves the current account using Wagmi's getAccount and returns a structured text response with address, addresses, chainId, and status.
    execute: async () => {
      const result = getAccount(wagmiConfig);
      return {
        content: [
          {
            type: "text",
            text: JSONStringify({
              address: result.address,
              addresses: result.addresses,
              chainId: result.chainId,
              status: result.status,
            }),
          },
        ],
      };
    },
  • Zod schema defining empty input parameters for the get-account tool.
    parameters: z.object({}),
  • Registers the get-account tool on the FastMCP server, defining name, description, schema, and handler.
    export function registerGetAccountTools(server: FastMCP, wagmiConfig: Config): void {
      server.addTool({
        name: "get-account",
        description: "Get the current account.",
        parameters: z.object({}),
        execute: async () => {
          const result = getAccount(wagmiConfig);
          return {
            content: [
              {
                type: "text",
                text: JSONStringify({
                  address: result.address,
                  addresses: result.addresses,
                  chainId: result.chainId,
                  status: result.status,
                }),
              },
            ],
          };
        },
      });
    };
  • Calls the registerGetAccountTools function as part of registering all tools.
    registerGetAccountTools(server, wagmiConfig);
  • src/index.ts:15-15 (registration)
    Top-level call to registerTools which includes get-account tool registration.
    registerTools(server, wagmiConfig);
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. 'Get' implies a read operation, but it doesn't disclose whether this requires authentication, what data is returned, or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 appropriately sized for a simple tool and immediately states the core functionality without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description should provide more context about what 'current account' means in this blockchain context and what data is returned. The simple statement is inadequate for a tool that likely returns important account information like address, balance, or chain details.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter information, and it correctly doesn't mention any parameters, earning a baseline score of 4 for this situation.

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 clearly states the verb 'Get' and the resource 'current account', making the purpose immediately understandable. However, it doesn't distinguish this from sibling tools like 'get-native-currency-balance' or 'get-token-balance' which also retrieve account-related information, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get-native-currency-balance' and 'get-token-balance' that retrieve specific account data, there's no indication of what 'current account' means or when this general tool is preferred over more specific ones.

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/Xiawpohr/metamask-mcp'

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