Skip to main content
Glama
mysql-readonly-mcp

mysql-readonly-mcp

by HaokaiLau

mysql_list_indexes

List indexes and ordered indexed columns for a single MySQL table to inspect schema, verify query performance, and understand available keys.

Instructions

List indexes and ordered indexed columns for one table.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table": "<table>"
    },
    "name": "mysql_list_indexes"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It conveys read-only intent implicitly via 'List' but does not state that this is a read operation, whether it requires database selection, or what happens on a missing table.

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, front-loaded verb, zero wasted words.

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

Completeness3/5

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

For a simple single-param read tool with no output schema, the description adequately conveys purpose but lacks the behavioral context (read-only nature, auth/db prerequisites) an agent would benefit from given no annotations.

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?

Only one parameter with 0% schema description coverage. The description names the scope ('one table') which maps to the single table param, but adds no syntax or format detail; with 0 params this baseline would be higher, but the param is undocumented.

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?

States a specific verb (List) and resource (indexes and ordered indexed columns) scoped to one table, which cleanly distinguishes it from siblings like mysql_describe_table and mysql_list_tables.

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 'for one table' scoping implies this is the index-inspection tool versus describe_table for columns, but no explicit when/when-not guidance or named alternatives are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.