Skip to main content
Glama

disconnect

Disconnect your MetaMask wallet from the MCPilot server to end blockchain interactions and secure your wallet connection.

Instructions

Disconnect the metamaks wallet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'disconnect' tool on the FastMCP server. Includes name, description, empty input schema (z.object({})), and the execute handler that calls wagmi's disconnect.
    server.addTool({
      name: "disconnect",
      description: "Disconnect the metamaks wallet",
      parameters: z.object({}),
      execute: async () => {
        await disconnect(wagmiConfig)
        return {
          content: [
            {
              type: "text",
              text: "Disconnect successfully",
            },
          ],
        }
      },
    });
  • The core handler logic for the disconnect tool, invoking the external wagmi disconnect function and returning a standardized MCP content response.
    execute: async () => {
      await disconnect(wagmiConfig)
      return {
        content: [
          {
            type: "text",
            text: "Disconnect successfully",
          },
        ],
      }
    },
  • Top-level invocation of the registerDisconnectTools function during MetaMask MCP server setup to enable the tool.
    registerDisconnectTools(server);
  • Zod schema defining empty parameters for the disconnect tool (no arguments required).
    parameters: z.object({}),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Disconnect') but doesn't explain what this entails—whether it terminates sessions, clears cached data, requires user confirmation, or has side effects like logging out from related services. This leaves significant gaps in understanding the tool's behavior.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse at a glance.

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 low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It states what the tool does but lacks context on behavior, usage scenarios, or effects, which is important for a mutation-like operation like disconnection. More detail would improve completeness.

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 appropriately doesn't discuss parameters, focusing instead on the tool's purpose. A baseline of 4 is applied since the schema fully handles parameter semantics.

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 action ('Disconnect') and the target resource ('the metamaks wallet'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'get-connect-uri' or 'show-connect-qrcode' which are related to connection functionality, leaving room for improvement in sibling distinction.

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, such as whether it should be used after certain operations or instead of other disconnection methods. There's no mention of prerequisites, exclusions, or contextual triggers for invocation.

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