Skip to main content
Glama
Rufflet

mysql-legacy-mcp

by Rufflet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

mysql_legacy_describe_table

Read-onlyIdempotent

List columns for a MySQL table with type, nullability, keys, comments, and collation. Use to inspect per-column metadata for legacy databases.

Instructions

Lists columns for database.table via SHOW FULL COLUMNS, including type, nullability, keys, comments, and collation. Use this for per-column metadata. For the full CREATE TABLE text and default charset use mysql_legacy_show_create_table. For index column order 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 cover read-only, idempotent, non-destructive behavior. The description adds value beyond that by revealing the specific SQL operation (SHOW FULL COLUMNS), the exact output fields, and clarifying it is not the tool for schema-level or index-level details. This is richer context than a bare annotation baseline.

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?

Three sentences, zero filler. The first sentence front-loads the primary function and output; the next two sentences provide targeted routing to alternatives. Every sentence earns its place.

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?

With only two required parameters, full schema coverage, and annotations covering safety, the description supplies the missing piece — what the result contains (columns, type, nullability, keys, comments, collation). No output schema exists, so the description reasonably fills that gap. Nothing needed for correct invocation is missing.

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% — both database and table have clear descriptions with length constraints. The description merely echoes 'database.table' without adding new semantic details about either parameter, so it stays at the baseline for fully documented schemas.

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 ('Lists columns'), a specific resource ('database.table'), and the underlying mechanism (SHOW FULL COLUMNS), then enumerates the metadata fields returned. It also distinguishes itself from two siblings by name, so an agent can clearly tell it apart.

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?

Explicitly states when to use this tool ('Use this for per-column metadata') and names the exact sibling alternatives for other use cases (show_create_table for full CREATE TABLE text, list_indexes for index column order). No inference required.

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