claude-database-tools

create_index

Improve database query performance by creating indexes on specified columns in MSSQL tables to optimize data retrieval and enforce uniqueness constraints.

Instructions

Creates an index on a specified column or columns in an MSSQL Database 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>",
      "indexName": "<indexName>",
      "columns": "<columns>"
    },
    "name": "create_index"
  }
}

Input Schema

Name	Required	Description
`tableName`	Yes	Name of the table to create index on (can include schema: schema.table)
`indexName`	Yes	Name for the new index
`columns`	Yes	Array of column names to include in the index
`isUnique`	No	Whether the index should enforce uniqueness (default: false)
`isClustered`	No	Whether the index should be clustered (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'creates an index' implies a schema mutation operation, the description doesn't address critical behavioral aspects: whether this requires specific database permissions, whether the operation is reversible, potential performance impacts during creation, or what happens if the index already exists. For a database mutation tool with zero annotation coverage, this represents significant gaps.

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 that clearly states the tool's purpose without unnecessary words. It's appropriately sized for a straightforward database operation and front-loads the essential information. Every word earns its place in conveying the core functionality.

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 database schema mutation tool with 5 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address behavioral implications, error conditions, performance considerations, or relationship to sibling tools. The agent would need to make assumptions about permissions, side effects, and appropriate usage contexts that aren't documented.

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 description mentions 'on a specified column or columns' which aligns with the 'columns' parameter, but doesn't add meaningful semantics beyond what the 100% schema coverage already provides. The schema descriptions comprehensively document each parameter's purpose, defaults, and requirements, so the description adds minimal value. The baseline score of 3 reflects adequate but not enhanced 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 ('creates an index') and target ('on a specified column or columns in an MSSQL Database table'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from potential alternatives like 'create_table' or 'get_table_alter_ddl' which might also involve database schema modifications.

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. With sibling tools like 'create_table', 'drop_table', and 'get_table_alter_ddl' available, there's no indication of when index creation is appropriate versus other schema operations or how it relates to data manipulation tools like 'insert_data' or 'update_data'.

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

Deploy Server