Skip to main content
Glama
sussa3007

MySql MCP Server

query

Execute SQL queries on MySQL databases directly using prepared statements. Manage data retrieval and enhance AI capabilities with structured database access.

Instructions

Execute an SQL query on the connected database.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNoParameters for prepared statements
sqlYesSQL query to execute

Implementation Reference

  • The handler for the 'query' tool. It extracts SQL and parameters from the request, calls executeQuery to run the query (with validation), and returns the results as JSON text content or an error.
    case "query": {
      try {
        const sql = request.params.arguments?.sql as string;
        const params = (request.params.arguments?.params as any[]) || [];
    
        // Execute query with validation
        const rows = await executeQuery(sql, params);
    
        return {
          content: [{ type: "text", text: JSON.stringify(rows, null, 2) }],
          isError: false
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text:
                error instanceof Error
                  ? error.message
                  : "Unknown error occurred"
            }
          ],
          isError: true
        };
      }
    }
  • The input schema for the 'query' tool, defining the expected parameters: sql (required string) and optional params (array of strings).
    inputSchema: {
      type: "object",
      properties: {
        sql: { type: "string", description: "SQL query to execute" },
        params: {
          type: "array",
          description: "Parameters for prepared statements",
          items: { type: "string" }
        }
      },
      required: ["sql"]
    }
  • src/index.ts:187-202 (registration)
    The registration of the 'query' tool in the ListTools response, including name, description, and input schema.
    {
      name: "query",
      description: "Execute an SQL query on the connected database.",
      inputSchema: {
        type: "object",
        properties: {
          sql: { type: "string", description: "SQL query to execute" },
          params: {
            type: "array",
            description: "Parameters for prepared statements",
            items: { type: "string" }
          }
        },
        required: ["sql"]
      }
    },
  • Helper function executeQuery that performs the actual database query execution, including read-only mode checks using getQueryType and isWriteOperation.
    async function executeQuery(sql: string, params: any[] = []): Promise<any> {
      const conn = await getConnection();
    
      // Check if in readonly mode and validate query type
      if (connectionConfig.readonly) {
        const queryType = getQueryType(sql);
        if (isWriteOperation(queryType)) {
          throw new Error(
            "Server is in read-only mode. Write operations are not allowed."
          );
        }
      }
    
      // Execute the query
      const [rows] = await conn.query(sql, params);
      return rows;
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, and the description only states 'execute an SQL query'. It does not disclose whether queries are read-only, side effects, error handling, or required permissions.

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 concise sentence, front-loading the essential action with no unnecessary words.

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, the description is incomplete. It misses details about return value format, safety, or limitations for a database query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and parameters are described within the schema. The description adds no additional meaning beyond what the schema already provides.

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 tool executes SQL queries, which is specific and aligns with the name. However, it does not differentiate from sibling tools like 'describe_table' or 'list_tables', but the purpose is unambiguous.

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 on when to use this tool versus alternatives like 'describe_table' or 'status'. Missing context on prerequisites or typical scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

Related Tools