Skip to main content
Glama
nilsir

MCP Server MySQL

by nilsir

create_index

Add an index to a MySQL table to improve query performance by specifying columns, index name, and optional uniqueness constraints.

Instructions

Create an index on a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYesTable name
indexNameYesIndex name
columnsYesColumn names to index
uniqueNoWhether this is a unique index
databaseNoDatabase name (optional)

Implementation Reference

  • The asynchronous handler function that implements the logic to create an index on a specified MySQL table. It constructs and executes a CREATE INDEX SQL statement using the provided table, index name, columns, unique flag, and optional database.
    async ({ table, indexName, columns, unique, database }) => {
      const p = await getPool();
    
      const tableName = database ? `\`${database}\`.\`${table}\`` : `\`${table}\``;
      const columnList = columns.map((c) => `\`${c}\``).join(", ");
      const uniqueStr = unique ? "UNIQUE " : "";
    
      await p.execute(
        `CREATE ${uniqueStr}INDEX \`${indexName}\` ON ${tableName} (${columnList})`
      );
    
      const output = {
        success: true,
        table,
        indexName,
        columns,
        unique: unique || false,
        database: database || null,
      };
    
      return {
        content: [
          {
            type: "text" as const,
            text: `Index ${indexName} created successfully on ${table}`,
          },
        ],
        structuredContent: output,
      };
    }
  • Zod schema for input validation of the create_index tool parameters: table, indexName, columns (array of strings), optional unique boolean, and optional database.
    {
      table: z.string().describe("Table name"),
      indexName: z.string().describe("Index name"),
      columns: z.array(z.string()).describe("Column names to index"),
      unique: z.boolean().optional().describe("Whether this is a unique index"),
      database: z.string().optional().describe("Database name (optional)"),
  • src/index.ts:521-561 (registration)
    The server.tool() call that registers the create_index tool, including name, description, input schema, and handler function.
    server.tool(
      "create_index",
      "Create an index on a table",
      {
        table: z.string().describe("Table name"),
        indexName: z.string().describe("Index name"),
        columns: z.array(z.string()).describe("Column names to index"),
        unique: z.boolean().optional().describe("Whether this is a unique index"),
        database: z.string().optional().describe("Database name (optional)"),
      },
      async ({ table, indexName, columns, unique, database }) => {
        const p = await getPool();
    
        const tableName = database ? `\`${database}\`.\`${table}\`` : `\`${table}\``;
        const columnList = columns.map((c) => `\`${c}\``).join(", ");
        const uniqueStr = unique ? "UNIQUE " : "";
    
        await p.execute(
          `CREATE ${uniqueStr}INDEX \`${indexName}\` ON ${tableName} (${columnList})`
        );
    
        const output = {
          success: true,
          table,
          indexName,
          columns,
          unique: unique || false,
          database: database || null,
        };
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Index ${indexName} created successfully on ${table}`,
            },
          ],
          structuredContent: output,
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits like permissions required, whether the operation is reversible, performance impact, or error conditions. This is inadequate for a mutation tool.

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, efficient sentence with zero wasted words, making it easy to parse and front-loaded with essential information. It earns its place without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavior, usage context, and expected outcomes, leaving significant gaps for an AI agent to operate effectively.

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 the schema fully documents all 5 parameters. The description adds no additional meaning beyond what's in the schema, meeting the baseline for high coverage but not enhancing parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('create') and resource ('index on a table'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'drop_index' or explain what an index does, which prevents a perfect score.

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 is provided on when to use this tool versus alternatives like 'alter_table' or 'drop_index', nor are prerequisites mentioned (e.g., needing an existing table). The description lacks context for tool 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/nilsir/mcp-server-mysql'

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