Skip to main content
Glama
neverinfamous

MySQL MCP Server

MySQL Read Query

mysql_read_query
Read-only

Execute read-only SELECT queries safely with prepared statements, supporting pagination and streaming results.

Instructions

Execute a read-only SQL query (SELECT). Uses prepared statements for safety.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
txNoAlias for transactionId
sqlNoAlias for query
txIdNoAlias for transactionId
queryNoSQL SELECT query to execute. Anti-Hallucination Hint: Must be a valid SQL query (e.g. 'SELECT * FROM users'), not just a table name.
cursorNoOpaque cursor for pagination (use nextCursor from previous response)
paramsNoQuery parameters for prepared statement
streamNoStream results via progress notifications instead of returning them all at once (requires client support)
chunkSizeNoNumber of rows per chunk when streaming (default: 10)
transactionIdNoOptional transaction ID for executing within a transaction

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?

Adds 'uses prepared statements' beyond annotations that declare readOnlyHint. Does not contradict annotations, but minimal additional behavioral context.

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?

Two sentences, no wasted words, front-loads the core purpose.

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?

Fails to mention key capabilities like streaming and transaction support, despite 9 parameters including those features. Output schema exists but description lacks holistic context.

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 helpful descriptions; description adds no extra meaning beyond what schema already provides.

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?

Clearly states 'Execute a read-only SQL query (SELECT)' with specific verb and resource. Distinguishes from write query siblings.

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?

Implies usage for SELECT queries via 'read-only', but no explicit when-not or alternative like mysql_write_query 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