Skip to main content
Glama
Sign In
MySQL MCP Server

MySQL MCP Server

by CobaltBlue3699
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

describe_table

Retrieve the full structure of a MySQL table including column names, types, and constraints.

Instructions

Get the structure of a specific 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": {
      "tableName": "<tableName>"
    },
    "name": "describe_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableNameYesThe name of the table to describe

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2-8

TDQS

B3.4/5.0
Behavior2/5

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

The description indicates a read-only operation ('Get'), but lacks details on error handling (e.g., missing table), authentication needs, or what exactly constitutes 'structure' (columns, types, constraints?). With no annotations, the description carries the full burden, which is insufficient.

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?

Single sentence, no unnecessary words. However, it could be slightly expanded to include what is returned without becoming verbose.

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?

Given the simplicity (1 parameter, no output schema), the description is adequate but does not mention what the structure includes or behavior if the table does not exist. A bit more detail would improve completeness.

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 only parameter, tableName, is fully described in the input schema (pattern, required, description). The tool description adds no additional meaning, so baseline score of 3 applies.

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 'Get the structure of a specific table' clearly states the action (Get) and the resource (structure of a specific table). It distinguishes from siblings like list_tables and execute_query, which list tables or run queries.

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?

No explicit guidance on when to use this tool instead of alternatives. It is implied that one uses it to retrieve table structure, but there are no when-not instructions or prerequisites mentioned.

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