Skip to main content
Glama
ImRieul

MySQL MCP Server

by ImRieul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

execute

Execute data modification SQL statements (INSERT, UPDATE, DELETE, DDL). Validate without executing by setting dryRun=true; confirm destructive operations like DROP or TRUNCATE before execution.

Instructions

Execute a data modification SQL statement (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, etc.). Set dryRun=true to validate without executing — uses EXPLAIN for DML, or previews the SQL for DDL. Always confirm destructive operations (DROP, TRUNCATE, DELETE without WHERE) with the user before executing. Not available in read-only mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sqlYesThe SQL statement to execute. SELECT statements are not allowed here; use the "query" tool instead.
dryRunNoIf true, validates the statement via EXPLAIN without executing it. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.3
    • addedInput schema / properties / dryRun
      Added value: +{
+  "description": "If true, validates the statement via EXPLAIN without executing it. Defaults to false.",
+  "type": "boolean"
+}
  2. First observedv1.0.2

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: it executes modifications, dryRun uses EXPLAIN for DML/previews for DDL, requires user confirmation for destructive ops, and is restricted in read-only mode.

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?

Three concise sentences, front-loaded with purpose. Each sentence adds necessary context without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and safety implications, the description covers purpose, usage, validation, and restrictions. While no output schema exists, the behavior is adequately described for an 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?

Schema coverage is 100% (baseline 3). The description adds value by explaining dryRun's behavior (EXPLAIN for DML, preview for DDL) and reinforcing that sql is for modification statements, not SELECT.

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 it executes data modification SQL statements (INSERT, UPDATE, DELETE, etc.) and explicitly distinguishes from the 'query' tool by excluding SELECT. It names specific SQL verbs, providing a precise scope.

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

Usage Guidelines5/5

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

It provides when to use (data modification SQL), when not to use (SELECT, use query instead), and includes safety guidelines: dryRun for validation, confirmation for destructive operations, and unavailability in read-only mode.

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