Skip to main content
Glama
Sign In
AI Data MCP

AI Data MCP

by ResetFull
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List MySQL tables

mysql_list_tables
Read-onlyIdempotent

List MySQL tables and views with pagination and name filtering, returning table type, engine, row estimate, and storage size. Read-only in all environments.

Instructions

List tables and views in a MySQL schema with pagination and an optional name filter. Returns table type, engine, row estimate, and storage size. This tool is read-only in every environment.

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": {
      "connection_id": "<connection_id>"
    },
    "name": "mysql_list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
schemaNoSchema to inspect. Defaults to the connection's configured database.
connection_idYesConfigured connection ID, for example prod-main or test-main.
name_containsNoOptional case-insensitive substring filter for table names.
response_formatNoResponse rendering: markdown for humans or json for programmatic processing.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0-alpha.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'read-only in every environment' largely restates structured data. The description does add non-redundant value by naming the returned fields (type, engine, row estimate, storage size) in the absence of an output schema; pagination is mentioned but its behavior (defaults, max page size) is left to 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the verb and scope, then return fields, then the safety note. No wasted clauses. The read-only sentence duplicates the annotations, costing it the top score, but it is short and clearly separated.

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 no output schema, the description usefully enumerates the returned columns, which is exactly what an agent cannot learn elsewhere. Read-only status, filtering and pagination are all signalled. Remaining gaps are minor: no guidance on empty results, no addressing of the openWorldHint (multiple configured connections), and no cross-reference to sibling tools.

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 67%, so baseline is 3. The description says 'pagination' and 'optional name filter', which maps to limit/offset/name_contains, but adds no semantics beyond what the schema already documents (case-insensitive substring, schema defaulting to the configured database). It provides no detail for the undescribed limit/offset bounds.

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?

States a specific verb and resource ('List tables and views in a MySQL schema') plus scope modifiers (pagination, name filter). An agent can tell this apart from mysql_query or mysql_describe_table by resource, but the description never names a sibling or the boundary between them, so it stops short of full differentiation.

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?

Usage is implied by the resource: enumerate tables/views in a schema, optionally narrowed by name_contains. There is no explicit when-to-use, no when-not-to-use, and no pointer to alternatives such as mysql_describe_table for column detail or mysql_query for row data, so routing is left to inference.

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

Deploy Server

Other Tools