Skip to main content
Glama
Darkstar326

MCP MySQL Server

by Darkstar326

mysql_disconnect

Terminate active MySQL database connections to manage resources and ensure security when database access is no longer required.

Instructions

Disconnect from the MySQL database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'mysql_disconnect' tool. It ends the MySQL connection pool if it exists, clears the config, and returns a success or no-connection message.
    private async handleDisconnect() {
      if (this.pool) {
        await this.pool.end();
        this.pool = null;
        this.config = null;
        return {
          content: [
            {
              type: "text",
              text: "Successfully disconnected from MySQL database",
            },
          ],
        };
      } else {
        return {
          content: [
            {
              type: "text",
              text: "No active MySQL connection to disconnect",
            },
          ],
        };
      }
    }
  • The tool schema definition including name, description, and empty input schema for 'mysql_disconnect' in the ListTools response.
    {
      name: "mysql_disconnect",
      description: "Disconnect from the MySQL database",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:263-264 (registration)
    The switch case registration that maps the 'mysql_disconnect' tool name to its handler function in the CallToolRequest handler.
    case "mysql_disconnect":
      return await this.handleDisconnect();
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. 'Disconnect' implies a state change operation, but the description doesn't specify whether this closes all connections or just the current session, whether it's reversible, what happens to pending transactions, or any cleanup behavior. For a state-changing tool with zero annotation coverage, this is inadequate.

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 that states exactly what the tool does with zero wasted words. It's appropriately sized for a zero-parameter tool and front-loads the essential information immediately.

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?

For a zero-parameter connection management tool with no output schema, the description covers the basic action but leaves important behavioral questions unanswered. Without annotations or output schema, the description should address more about what 'disconnect' actually means operationally - whether it's immediate, what gets cleaned up, and what state the system is left in.

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 zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description correctly implies no parameters are needed, establishing baseline 4. No additional parameter semantics are required or provided.

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 target resource ('from the MySQL database'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings beyond the obvious - it doesn't explain why you'd use this versus simply not calling mysql_connect or letting connections time out naturally.

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. It doesn't mention prerequisites (must be connected first), doesn't specify when disconnection is necessary versus optional, and doesn't reference sibling tools like mysql_connect that establish the connection being terminated.

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/Darkstar326/mcp-mysql'

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