Skip to main content
Glama
neverinfamous

MySQL MCP Server

MySQL Create Table

mysql_create_table

Creates a MySQL table with specified columns, data types, constraints, storage engine, charset, and collation settings.

Instructions

Create a new table with specified columns, engine, and charset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoTable name
tableNoAlias for name
engineNoStorage engineInnoDB
charsetNoCharacter setutf8mb4
collateNoCollationutf8mb4_unicode_ci
columnsNoColumn definitions. Anti-Hallucination Hint: Must be an array of objects (e.g. [{name: 'id', type: 'INT'}]), not a key-value object.
commentNoTable comment
tableNameNoAlias for name
ifNotExistsNoAdd IF NOT EXISTS clause

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, QUERY_ERROR)
dataNo
errorNoError message if operation failed
detailsNoAdditional error context
metricsNoToken estimation metrics
successYesWhether the operation succeeded
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
Behavior3/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which is consistent with a create operation. The description adds that it creates a table with specified options but does not elaborate on side effects, permissions, or behavior on existing tables. It neither contradicts annotations nor adds significant depth.

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 a single, front-loaded sentence with 12 words. Every word earns its place; there is no redundancy or waste.

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?

Given the presence of an output schema (signal says true) and full parameter descriptions, the tool is fairly complete for a create operation. However, it could mention that columns should be provided and that the table might fail if it already exists without ifNotExists. Still, the input schema covers most details.

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%, so baseline is 3. The description mentions a few parameters (columns, engine, charset) but does not add extra meaning beyond the schema definitions. It does not clarify that columns is effectively required despite no required parameters listed.

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 clearly states the verb 'create', the resource 'table', and specifies key aspects ('columns, engine, and charset'). It distinguishes this tool from sibling tools like mysql_drop_table or mysql_describe_table.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., database must exist) or when not to use it. No exclusions or context are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/neverinfamous/mysql-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server