Skip to main content
Glama
neverinfamous

MySQL MCP Server

MySQL JSON Set

mysql_json_set

Update values in JSON columns at specified paths by providing table, column, path, value, and WHERE clause.

Instructions

Set or update values in JSON columns at specified paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colNoAlias for column
sqlNoAlias for where
valNoAlias for value
nameNoAlias for table
pathNoJSON path to set
queryNoAlias for where
rowIdNoAlias for where (used with idColumn)
tableNoTable name (Anti-Hallucination: Pass 'table', not 'tableName')
valueNoValue to set
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
Behavior3/5

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

Annotations already indicate the tool is mutating (readOnlyHint=false) but not destructive (destructiveHint=false). The description adds the behavioral detail that it 'sets or updates', which is consistent with mutations. No additional behavioral traits (e.g., path creation, error behavior) are disclosed beyond what annotations imply.

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 one short sentence, free of extraneous content. It is concise and to the point, though it could be extended slightly without losing conciseness to add differentiating context.

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?

Despite having an output schema and high parameter coverage, the description lacks overall context. It does not explain how this tool differs from other JSON modification siblings, nor does it clarify the behavior of the many aliased parameters. The description is too minimal to fully inform an agent.

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 description coverage is 100%, so the schema already explains all parameters. The tool description does not add any extra meaning or context for parameters, leaving interpretation to the schema. Baseline 3 is appropriate.

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?

The description clearly states the action ('set or update') and the target ('values in JSON columns at specified paths'). It uses a specific verb and resource. However, it does not distinguish this tool from siblings like mysql_json_insert, mysql_json_replace, or mysql_json_remove, which also modify JSON columns.

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?

The description provides no guidance on when to use this tool versus alternatives. Among siblings, there are many JSON manipulation tools, but no mention of when JSON_SET is appropriate (e.g., creates missing paths, replaces existing) vs JSON_INSERT or JSON_REPLACE.

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