Skip to main content
Glama
neverinfamous

MySQL MCP Server

MySQL JSON Extract

mysql_json_extract
Read-only

Extract values from JSON columns in MySQL using JSON path expressions, enabling direct access to nested data.

Instructions

Extract values from JSON columns using JSON path expressions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colNoAlias for column
sqlNoAlias for where
nameNoAlias for table
pathNoJSON path (e.g., $.name or $[0])
limitNoMaximum rows to return
queryNoAlias for where
rowIdNoAlias for where (used with idColumn)
tableNoTable name (Anti-Hallucination: Pass 'table', not 'tableName')
whereNoWHERE clause for filtering rows
columnNoJSON column name
filterNoAlias for where
idColumnNoAlias for where (used with rowId)
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 declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds method context ('using JSON path expressions') but does not explain behavioral details like return format, error handling, or limitations. Minimal 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 sentence (11 words), which is front-loaded but overly brief for a tool with 14 parameters and many aliases. It lacks necessary detail, making it insufficient for an agent to use correctly without additional context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (14 parameters, many aliases, no required params, and an output schema not described), the description is woefully incomplete. It does not explain parameter roles, JSON path syntax, or output structure. The agent cannot infer usage from this description alone.

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 description coverage is 100%, but most parameter descriptions are simply 'Alias for X', which adds little meaning. The global description does not explain parameters. The agent is left with cryptic aliases and no guidance on which to use. Baseline is 3 due to high coverage, but the poor quality of descriptions reduces the score.

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 tool extracts values from JSON columns using JSON path expressions, which is a specific verb and resource. However, it does not differentiate from similar siblings like mysql_json_get, so it loses a point for lack of sibling distinction.

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 the many other JSON tools in the sibling list. It does not mention alternatives, prerequisites, or exclusion criteria.

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