Skip to main content
Glama
neverinfamous

MySQL MCP Server

MySQL JSON Normalize

mysql_json_normalize
Read-only

Extract all unique keys across JSON documents in a column to normalize and standardize the structure for analysis.

Instructions

Normalize JSON column structure by extracting all unique keys across documents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colNoAlias for column
nameNoAlias for table
limitNoMaximum rows to process
rowIdNoAlias for where (used with idColumn)
tableNoTable name. Note: This tool normalizes an existing JSON column in a table, it does not normalize raw JSON strings.
whereNoWHERE clause
columnNoJSON column name
filterNoAlias for where
idColumnNoAlias for where (used with rowId)
tableNameNoAlias for table

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 annotations already indicate read-only and non-destructive behavior. The description adds the method (extracting unique keys) but does not elaborate on side effects, authorization needs, or output structure beyond what annotations cover.

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?

Single sentence that front-loads the key action and resource. No extraneous words, every phrase adds value.

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 10 parameters (many aliases) and an output schema, the description is too brief. It does not explain how to use the parameters effectively, what the output looks like, or how aliases relate. More context is needed for an agent to correctly invoke the tool.

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 baseline is 3. The description does not add parameter-level detail beyond the schema descriptions, which are mostly minimal aliases (e.g., 'Alias for column'). The overall purpose helps but does not compensate for shallow per-parameter docs.

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 verb (normalize), resource (JSON column), and method (extracting unique keys). This distinguishes it from sibling JSON tools like mysql_json_keys (which just lists keys) and mysql_json_extract (which retrieves values).

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 the tool is for schema discovery of JSON columns, but it does not explicitly state when to use it versus alternatives (e.g., mysql_json_keys or mysql_json_stats). No when-not-to-use guidance 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