Skip to main content
Glama
neverinfamous

MySQL MCP Server

MySQL Create Index

mysql_create_index

Create indexes on MySQL tables with support for BTREE, HASH, FULLTEXT, and SPATIAL index types. Define unique indexes and add IF NOT EXISTS clause.

Instructions

Create an index on a table. Supports BTREE, HASH, FULLTEXT, and SPATIAL index types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoIndex name
typeNoIndex type
tableNoTable name
uniqueNoCreate unique index
columnsNoColumns to index. Anti-Hallucination Hint: Must be an array of strings (e.g. ['id', 'status']), not a single string or an array of objects.
indexNameNoAlias for name
tableNameNoAlias for table
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 (mutation) and destructiveHint=false, which are consistent with the description. However, the description does not disclose potential side effects like table locking, prerequisite table existence, or performance impact, which would add value beyond the 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 extremely concise: two sentences, 14 words. It front-loads the primary action and lists supported types. Every word contributes meaning without redundancy.

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 tool's 8 parameters (some with aliases), the description is adequate for a straightforward DDL operation. It mentions supported index types and the schema covers details. However, it could be more complete by noting prerequisites or side effects, so a slight deduction.

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 has 100% parameter description coverage, so the baseline is 3. The description adds little beyond the schema; it only reiterates the supported index types (already in the enum). No extra meaning is provided for other parameters like name, table, columns, etc.

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 tool's purpose: 'Create an index on a table.' It also lists supported index types, distinguishing it from sibling tools that perform other operations like reading indexes or dropping tables.

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 does not provide any guidance on when to use this tool versus alternatives, such as when to create an index vs. using write_query or other DDL tools. No exclusions or context are given.

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