Skip to main content
Glama
Liu-creators

MySQL MCP

by Liu-creators

create_table

Define a new MySQL table by providing its name and column definitions (e.g., 'id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(100)'). Optionally specify a database connection for custom configuration.

Instructions

创建新表

Args:
    table_name: 表名
    columns_def: 列定义,例如 "id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(100), age INT"
    db_config: 数据库连接配置参数,如果为None则使用默认配置
    
Returns:
    包含创建结果的字典

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_nameYes
columns_defYes
db_configNo
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions the return value ('包含创建结果的字典') but lacks details on authentication, rate limits, side effects (e.g., what happens if table exists), or error conditions.

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?

The description is reasonably concise with a clear Args/Returns structure. It avoids unnecessary text, but could be slightly more compact without losing information.

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?

For a table creation tool with no output schema and no annotations, the description covers the basic function and parameters. However, it lacks warnings about table existence, permission requirements, or transactional behavior, which limits 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?

Schema provides no descriptions (0% coverage), so the description must compensate. It explains db_config's purpose and default behavior, and gives a concrete example for columns_def. However, table_name is only described as '表名' (table name), which adds little value beyond the schema's title.

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 '创建新表' (create new table), which is a specific verb+resource. It distinguishes itself from sibling tools like delete_data, describe_table, etc., by focusing on table creation.

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?

No guidance on when to use this tool versus alternatives (e.g., insert_data, update_data). There is no mention of prerequisites, when not to use, or comparisons with siblings, leaving the agent without context for selection.

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/Liu-creators/mysql-mcp'

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