Skip to main content
Glama
neverinfamous

MySQL MCP Server

MySQL JSON Update

mysql_json_update

Update a JSON value in a MySQL table column by specifying the JSON path and a WHERE clause to identify the target row.

Instructions

Simple JSON value update by row ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colNoAlias for column
sqlNoAlias for where
valNoAlias for value
nameNoAlias for table
pathNoJSON path to update
queryNoAlias for where
rowIdNoAlias for where (used with idColumn)
tableNoTable name (Anti-Hallucination: Pass 'table', not 'tableName')
valueNoNew value
whereNoWHERE clause to identify rows (REQUIRED. Anti-Hallucination: Pass 'where', not 'query' or 'sql')
columnNoJSON column name
filterNoAlias for where
idColumnNoAlias for where (used with rowId)
conditionNoAlias for where
tableNameNoAlias for table
columnNameNoAlias for column

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
Behavior2/5

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

Annotations provide minimal information. The description does not disclose behavioral traits such as whether updates are atomic, what happens if the row does not exist, or permission requirements. No added value beyond annotations.

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

Conciseness3/5

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

The description is a single short sentence, which is concise but misses necessary detail for effective use. It is front-loaded but too brief to be fully informative.

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 complexity (16 parameters with many aliases) and the lack of output schema details, the description is insufficient. It does not explain how to use the tool effectively, nor does it distinguish it from multiple sibling JSON tools.

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

Parameters2/5

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

Schema coverage is 100%, but the description does not clarify the confusing array of parameters (many aliases). The description itself adds no parameter semantics; the schema's parameter descriptions are vague (e.g., 'Alias for where'). Baseline 3 is lowered due to lack of helpful context.

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?

Description clearly states the action (update) and resource (JSON value) with a specific condition (by row ID). However, it does not differentiate from similar sibling tools like mysql_json_set or mysql_json_replace, which also update JSON values.

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. No mention of prerequisites, limitations, or exclusions. The description lacks usage context entirely.

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