Skip to main content
Glama
neverinfamous

MySQL MCP Server

MySQL Conditional Update

mysql_conditional_update

Updates a row only when its _version matches the expected version, avoiding lost updates in multi-agent environments.

Instructions

Update a row only if its _version matches expectedVersion. Prevents lost updates in multi-agent environments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAlias for rowId
dataNoColumn-value pairs to update
nameNoAlias for table
rowIdNoAlias for conditions. Shorthand for updating a single row by primary key.
tableNoTable to update
updatesNoAlias for data
versionNoAlias for expectedVersion
idColumnNoPrimary key column name. Defaults to 'id' if not provided. Used with rowId alias.
conditionNoAlias for conditions (can be object, string, or number)
tableNameNoAlias for table
conditionsNoConditions identifying the row (e.g. primary key). Anti-Hallucination Hint: Must be an array of objects (e.g. [{column: 'id', value: 1}]), not a string.
expectedVersionNoThe _version value currently expected. Update fails if this does not match.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, QUERY_ERROR)
dataNo
errorNoError message if operation failed
detailsNoAdditional error context
metricsNoToken estimation metrics
successYesWhether the operation succeeded
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
Behavior3/5

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

The description mentions the version-checking behavior, which adds context beyond the false annotations. However, it does not disclose what happens on version mismatch, whether the update is atomic, or if it updates only one row despite the conditions array allowing multiple. The behavior is partially transparent but lacks key details.

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 extremely concise, consisting of two sentences that front-load the core purpose and a key benefit. Every sentence adds value without redundancy.

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 tool's complexity (12 parameters, many aliases, nested conditions array), the description is too brief. It does not explain the alias system, the expected format of conditions, or the requirement that the _version column exist in the table. The presence of an output schema does not compensate for these gaps.

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%, so every parameter has a description. The tool description does not add any parameter-specific information beyond what is already in the schema. The schema descriptions are mostly alias references, which are functional but minimal.

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: 'Update a row only if its _version matches expectedVersion.' It distinguishes this tool from other MySQL update tools (like mysql_write_query) by specifying the optimistic locking mechanism, making the purpose specific and unambiguous.

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

Usage Guidelines3/5

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

The description implies usage in multi-agent environments to prevent lost updates, but it does not explicitly state when to prefer this tool over alternatives like mysql_write_query. No direct guidance on prerequisites or exclusions is provided.

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

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