Skip to main content
Glama

get-account

Retrieve the current blockchain account address from MetaMask wallet for secure AI-powered transactions and interactions.

Instructions

Get current account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute handler for the 'get-account' tool. Retrieves the current account information using wagmi's getAccount function with the configured wagmiConfig and returns a formatted text response containing 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,
            }),
          },
        ],
      }
    },
  • The registration function for the 'get-account' tool. Adds the tool to the FastMCP server, specifying name, description, empty input schema (z.object({})), and the execute handler.
    export function registerGetAccountTools(server: FastMCP): void {
      server.addTool({
        name: "get-account",
        description: "Get 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,
                }),
              },
            ],
          }
        },
      });
    };
  • Top-level call to register the 'get-account' tool on the main FastMCP server instance.
    registerGetAccountTools(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but it doesn't specify if this requires authentication, returns cached or live data, has rate limits, or what the output format might be. This is a significant gap for a tool with zero annotation coverage.

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 extremely concise with just three words, front-loaded with the core action. There's no wasted language, making it efficient for quick understanding, though this brevity contributes to gaps in other dimensions.

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 complexity of blockchain tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'current account' entails (e.g., address, balance, nonce) or the return values, leaving the agent with insufficient information to use the tool effectively in this context.

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, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but this is appropriate given the lack of inputs, warranting a baseline score above minimum viable.

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

Purpose3/5

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

The description 'Get current account' states a clear verb ('Get') and resource ('current account'), but it's vague about what 'current account' means in this blockchain context. It doesn't distinguish this tool from siblings like 'get-ens-address' or 'get-ens-name' which might also retrieve account-related information, leaving ambiguity about the specific type of account being retrieved.

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 siblings like 'get-ens-address' and 'get-ens-name' that might retrieve account details, there's no indication of whether this tool returns a wallet address, account metadata, or something else, nor any prerequisites or context for its use.

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/mcpilot'

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