Skip to main content
Glama
Secure MySQL MCP Server

Secure MySQL MCP Server

by Kavi-200312

list_tables

Lists all tables and views in the configured development database, letting AI clients discover schema objects before writing queries.

Instructions

List all tables and views in the development database.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseNoOptional database name (must match configured development database).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. 'List' implies a safe read, but the description doesn't state whether system tables are excluded, whether the output is names only or includes metadata, or any permission requirement — it does add that views are included, which is useful beyond the schema.

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?

A single front-loaded sentence with no redundant wording; the resource and the scope constraint are both stated immediately. Nothing could be removed without losing information.

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?

For a one-optional-parameter, read-only listing tool with no output schema, the definition covers purpose and scope adequately. The main remaining gap is the return shape (bare names vs. table metadata plus views), which is minor but would help an agent plan next steps.

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 description coverage is 100% with a single optional 'database' parameter that the schema already documents, including the constraint that it must match the configured development database. The description adds only the 'development' framing, which the schema already encodes, so the baseline 3 applies.

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?

Names a specific verb and resource ('List all tables and views') and constrains scope to the development database, so the agent knows exactly what it enumerates. It doesn't explicitly distinguish itself from siblings like list_databases or describe_table, but the objects it targets are unambiguous.

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 scope ('development database') implies this is a schema-discovery/read step rather than a query or write, which aligns with siblings such as read_query and write_query. However, it never states when to prefer this over list_databases or describe_table, nor any exclusion conditions, leaving routing to inference.

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