Skip to main content
Glama

disconnectFromServer

Terminate the connection to the Minecraft server managed by MCP Minecraft Remote, ending remote control and interaction sessions.

Instructions

Disconnect from the Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that disconnects the bot from the Minecraft server by calling bot.quit(), updating the connection state, and returning appropriate responses.
    async () => {
      if (!botState.isConnected || !botState.bot) {
        return createNotConnectedResponse()
      }
    
      try {
        botState.bot.quit()
        updateConnectionState(false, null)
        return createSuccessResponse(
          'Successfully disconnected from the server.'
        )
      } catch (error) {
        return createErrorResponse(error)
      }
    }
  • Registers the 'disconnectFromServer' tool with its description, empty input schema, and inline handler function within registerConnectTools.
    server.tool(
      'disconnectFromServer',
      'Disconnect from the Minecraft server',
      {},
      async () => {
        if (!botState.isConnected || !botState.bot) {
          return createNotConnectedResponse()
        }
    
        try {
          botState.bot.quit()
          updateConnectionState(false, null)
          return createSuccessResponse(
            'Successfully disconnected from the server.'
          )
        } catch (error) {
          return createErrorResponse(error)
        }
      }
    )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Disconnect') but doesn't explain what this entails—whether it ends a session, affects other tools, requires reconnection, or has side effects. This is a significant gap for a tool that likely changes state.

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 waste—it states exactly what the tool does without unnecessary words. It's front-loaded and efficiently communicates the core purpose.

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, and the tool's likely state-changing nature (disconnecting from a server), the description is incomplete. It doesn't address behavioral aspects like what happens after disconnection, error conditions, or interaction with other tools, leaving gaps for the agent.

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 mention parameters, aligning with the schema, which is sufficient for this case.

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 from') and resource ('the Minecraft server'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'connectToServer', but the verb 'Disconnect' inherently contrasts with 'connect', providing implicit 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?

No guidance is provided on when to use this tool versus alternatives or in what context. The description is a standalone statement without any usage instructions, prerequisites, or exclusions, leaving the agent to infer timing from the tool name alone.

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/nacal/mcp-minecraft-remote'

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