Run a read-only SELECT query on legacy MySQL 5.0–5.6 with enforced row and byte limits, rejecting SELECT INTO and locking reads for safe data retrieval.
Executes exactly one read-only SELECT statement. SELECT INTO and locking reads are rejected; results are limited by MYSQL_LEGACY_MAX_ROWS and MYSQL_LEGACY_MAX_RESULT_BYTES.
| Name | Required | Description | Default |
|---|---|---|---|
| sql | Yes | One MySQL 5.1-compatible SELECT statement. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It discloses read-only behavior, rejects SELECT INTO and locking reads, and names result limits. It could also explain what happens when a limit is exceeded, but the core safety and constraints are transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tightly written sentences with the main action front-loaded. Every clause adds useful constraint information, with no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read-only tool, the description covers the key invocation constraints and safety behavior. There is no output schema, and the description does not specify the return shape or limit-exceeded behavior, but this is a minor gap given the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already fully documents the single sql parameter. The description adds context about read-only and compatibility but does not meaningfully extend parameter-level semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Executes'), a precise resource ('exactly one read-only SELECT statement'), and the key scoping rule. This clearly distinguishes it from sibling metadata tools like mysql_legacy_list_tables or mysql_legacy_describe_table.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description makes clear this tool is for executing SELECT queries, while the sibling names cover connectivity, listing, and schema inspection. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to choose correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.