mysql-mcp-server

database_execute_sql

Execute SQL statements on the active database connection. Use optional parameters for prepared statements to run queries safely.

Instructions

Execute a single SQL statement on the active database connection

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sql": "<sql>"
    },
    "name": "database_execute_sql"
  }
}

Input Schema

Name	Required	Description	Default
`sql`	Yes	SQL statement to execute
`params`	No	Optional parameters for prepared statement

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only says 'execute' and does not disclose whether the SQL may be read-only or mutating, what side effects may occur, or what the return value looks like. The active connection context is a minor prerequisite but insufficient.

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, front-loaded sentence with no unnecessary words. It states the action, resource, and key constraints efficiently.

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?

For an arbitrary SQL execution tool with no output schema and no annotations, the description omits crucial return value information (e.g., result sets, affected rows), error behavior, and side effects. The sibling tool names suggest variants but provide no usage guidance. The description is too sparse to fully inform an agent about executing a potentially destructive statement safely.

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?

Schema coverage is 100% with descriptions for both parameters, but the tool description adds the important constraint that the sql parameter must contain a single statement (not a script/batch). This adds semantic value beyond the schema's generic 'SQL statement to execute'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Execute') and resource ('SQL statement') with a clear scope qualifier ('single', 'active database connection'). It effectively distinguishes this tool from sibling tools like database_execute_script and database_execute_batch, which handle multiple statements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'single SQL statement' clearly implies usage for one statement only, distinguishing it from script/batch variants. It also hints at a prerequisite (active database connection). However, it does not explicitly name alternatives or state exclusions.

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

Deploy Server