Skip to main content
Glama
neverinfamous

MySQL MCP Server

MySQL JSON Replace

mysql_json_replace

Update JSON column values by replacing only when the specified JSON path exists, ensuring no unintended inserts.

Instructions

Replace values in JSON columns only if the path exists.

Input Schema

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

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

Annotations already indicate it is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds the condition of path existence but lacks details on error handling, permissions, or side effects. With annotations covering safety, a score of 3 is appropriate.

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 sentence, concise and front-loaded with the key purpose. No wasted words, but could benefit from slightly more structure without losing conciseness.

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, many aliases, numerous siblings), the description is too brief. It does not clarify parameter relationships, primary vs. alias usage, or differentiate from siblings. The output schema exists but is not described.

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% with descriptions for each parameter, but many descriptions are just 'Alias for ...' without explaining actual usage. The tool description does not add extra parameter semantics, so baseline 3 is correct.

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 ('replace values') and the specific condition ('only if the path exists'), distinguishing it from siblings like json_insert and json_set.

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 explicit guidance on when to use this tool vs alternatives like mysql_json_set or mysql_json_insert. The condition is implied but alternatives are not mentioned.

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