Skip to main content
Glama
Rufflet

mysql-legacy-mcp

by Rufflet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

mysql_legacy_show_create_table

Read-onlyIdempotent

Retrieves the DDL statement (SHOW CREATE TABLE) for a given database.table, including the parsed default charset, to inspect table definitions.

Instructions

Returns SHOW CREATE TABLE for database.table plus the parsed default charset. Use this for DDL text. For per-column types and collation use mysql_legacy_describe_table. For unique/non-unique keys use mysql_legacy_list_indexes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYesMySQL table or view name, 1–64 characters.
databaseYesMySQL database name, 1–64 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.1
    • addedInput schema / properties / database / description
      Added value: +"MySQL database name, 1–64 characters."
    • removedInput schema / properties / table / $ref
      Removed value: -"#/properties/database"
    • addedInput schema / properties / table / description
      Added value: +"MySQL table or view name, 1–64 characters."
    • addedInput schema / properties / table / maxLength
      Added value: +64
    • addedInput schema / properties / table / minLength
      Added value: +1
    • addedInput schema / properties / table / type
      Added value: +"string"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered without needing restatement. The description adds meaningful behavioral context by specifying that it returns the DDL text and a parsed charset. No contradiction exists between description and annotations.

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 three concise, purposeful sentences: core behavior first, usage directive second, alternatives third. Every sentence earns its place and there is no filler or repetition.

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

Completeness5/5

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

This is a simple two-parameter read-only tool with full schema coverage and clear sibling alternatives. There is no output schema, but the description covers what is returned (DDL text plus parsed charset). An agent has everything needed to select and invoke the tool correctly.

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?

The input schema covers both parameters at 100%: each has a name, type, length constraints, required status, and description. The description adds only the implicit database.table qualification, which is minor. With full schema coverage, baseline 3 is appropriate.

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 states the specific verb 'Returns' and the exact resource 'SHOW CREATE TABLE for database.table', plus the 'parsed default charset' as additional output. It also explicitly differentiates the tool from mysql_legacy_describe_table and mysql_legacy_list_indexes, making its purpose unambiguous.

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

Usage Guidelines5/5

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

The description gives direct usage guidance: 'Use this for DDL text.' It then names the precise alternatives and their conditions: per-column types/collation go to mysql_legacy_describe_table, and unique/non-unique keys go to mysql_legacy_list_indexes. This fully routes an agent to the correct tool.

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