Centia MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

deleteIndex

Deletes a specified index from a database table within a given schema, removing the index structure and freeing resources.

Instructions

Delete index(es).

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": {
      "schema": "<schema>",
      "table": "<table>",
      "index": "<index>"
    },
    "name": "deleteIndex"
  }
}

Input Schema

Name	Required	Description
`schema`	Yes	Name of schema
`table`	Yes	Name of table
`index`	Yes	Index name(s)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 26, 2026

TDQS

D1.9/5.0

Behavior1/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the action (delete) without revealing side effects, reversibility, or error handling. Critical information is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (two words) but not effectively concise; it under-specifies the tool's function. It is not front-loaded with essential details, making it minimally informative.

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

Completeness1/5

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

Given the complexity (3 required params, no output schema, no annotations), the description fails to cover return values, error conditions, or any operational constraints. It is completely inadequate for an agent to use reliably.

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%, with each parameter having minimal descriptions like 'Name of schema'. The tool description adds the plural hint 'index(es)', which aligns with the schema's 'name(s)', but does not substantively enhance understanding beyond the schema.

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

Purpose2/5

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

The description 'Delete index(es).' is essentially a tautology of the tool name 'deleteIndex'. It restates the function without adding specificity about what kind of index or context, thus failing to provide clear purpose beyond the name.

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 'deleteConstraint' or 'postIndex'. There is no mention of prerequisites, scope, or exclusions.

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