Skip to main content
Glama
Sign In
mysql-mcp-server

mysql-mcp-server

by eeantoss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

database_execute_batch

Execute multiple SQL statements as a single batch on the active database connection, including support for optional parameters.

Instructions

Execute multiple SQL statements as a batch 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": {
      "batch": "<batch>"
    },
    "name": "database_execute_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchYesArray of SQL statements with optional parameters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It reveals the dependency on an active connection but does not disclose transaction behavior, error handling, whether results are returned, or whether the batch is atomic. This is a significant gap for a mutation-capable SQL tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single clear sentence with no wasted words. It is appropriately front-loaded, though it sacrifices necessary detail for brevity.

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?

The tool has no output schema and no annotations, and batch SQL execution is complex. The description only notes the active connection requirement, leaving out behavior on failure, return values, and the distinction from script execution. This is insufficient for an agent to use the tool correctly.

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?

The schema description covers 100% of parameters with the 'batch' array described. The tool description does not add additional parameter guidance beyond restating that it executes multiple statements. Baseline of 3 is appropriate.

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 clearly states the action (execute), the object (multiple SQL statements as a batch), and the scope (active database connection). It distinguishes from sibling database_execute_sql, which likely handles a single statement, though it doesn't explicitly differentiate from database_execute_script.

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 given on when to use this tool instead of database_execute_sql or database_execute_script. The word 'batch' implies multiple statements, but there is no explicit statement of prerequisites (e.g., must have an active connection) or when to use alternatives.

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