Skip to main content
Glama
xingyuli

just-a-mysql-mcp

by xingyuli

mysql_query

Runs a single read-only SQL statement against a bound MySQL database. Supports SELECT, SHOW, DESCRIBE, and EXPLAIN queries with configurable row limits.

Instructions

Run one read-only SQL statement against the bound database.

Allowed: SELECT (including WITH…SELECT), SHOW, DESCRIBE/DESC, EXPLAIN.
Results are capped (default 100 rows, max 1000); truncation is explicit.

Args:
    sql: A single read-only SQL statement
    limit: Max rows to return (default 100, max 1000)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sqlYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It explicitly states the operation is read-only, lists allowed statements, and discloses row cap and truncation behavior. This adds significant context beyond the basic action.

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?

The description is concise and well-structured: a clear one-sentence purpose, a succinct 'Allowed' list, a note on row caps, and an args list. Every sentence adds value with no redundancy.

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

Completeness4/5

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

With an output schema present, the description covers the tool's purpose, allowed operations, row-cap behavior, and parameter semantics. Minor gaps include no mention of error handling or interaction with sibling tools, but these are not essential given the overall clarity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero description coverage, but the description fully compensates by defining sql as 'A single read-only SQL statement' and limit as 'Max rows to return (default 100, max 1000)', adding clarity, constraints, and defaults for both parameters.

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 opens with 'Run one read-only SQL statement against the bound database', providing a specific verb, resource, and scope. It lists allowed statement types and is clearly distinguishable from sibling tools like list_tables and describe_table, which focus on schema introspection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states when to use the tool by listing allowed statement types (SELECT, SHOW, DESCRIBE, EXPLAIN) and noting result caps. It does not explicitly reference sibling tools or exclusion cases, but the context is clear enough for an agent to decide.

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/xingyuli/just-a-mysql-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server