Skip to main content
Glama

disconnect

Disconnect your wallet from the MetaMask MCP server to end the session and secure your blockchain interactions.

Instructions

Disconnect the wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute handler for the 'disconnect' tool, which calls wagmi's disconnect function and returns a success text response.
    execute: async () => {
      await disconnect(wagmiConfig);
      return {
        content: [
          {
            type: "text",
            text: "Disconnect successfully",
          },
        ],
      };
    },
  • Direct registration of the 'disconnect' tool using FastMCP's addTool method, including name, description, empty schema, and handler.
    server.addTool({
      name: "disconnect",
      description: "Disconnect the wallet.",
      parameters: z.object({}),
      execute: async () => {
        await disconnect(wagmiConfig);
        return {
          content: [
            {
              type: "text",
              text: "Disconnect successfully",
            },
          ],
        };
      },
    });
  • Invocation of registerDisconnectTools as part of the batched tools registration.
    registerDisconnectTools(server, wagmiConfig);
  • src/index.ts:15-15 (registration)
    Top-level call to register all tools, which indirectly registers the 'disconnect' tool.
    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 the full burden. 'Disconnect' suggests a mutation or state change, but it doesn't disclose behavioral traits such as whether it's reversible, requires authentication, affects other sessions, or has side effects like clearing cached data. This leaves critical gaps for an agent to understand the tool's impact.

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 directly states the tool's purpose, making it easy to parse quickly. This is an example of optimal conciseness for a simple tool.

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 a wallet disconnect operation (likely a mutation with state changes), the description is incomplete. No annotations or output schema exist to clarify behavior or results. It fails to address what happens post-disconnect, error conditions, or confirmation of success, leaving the agent with insufficient 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param details, which is appropriate here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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 'Disconnect the wallet' clearly states the action (disconnect) and resource (wallet), but it's vague about what 'disconnect' entails—does it log out, clear session, or revoke permissions? It distinguishes from siblings like 'get-connect-uri' or 'show-connect-qrcode', but lacks specificity compared to tools like 'sign-message' or 'send-transaction'.

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. It doesn't mention prerequisites (e.g., must be connected first), exclusions, or related tools like 'get-connect-uri' for reconnection. The context is implied from the tool name alone, but explicit usage instructions are missing.

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