Skip to main content
Glama
AIops-tools

postgres-aiops

by AIops-tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

drop_index

Safely drop a PostgreSQL index by capturing its definition for reversible undo, supporting dry-run preview and concurrent dropping to avoid table locks.

Instructions

[WRITE][risk=high] Drop an index. Reversible: captures pg_get_indexdef first.

Before dropping, the exact index definition is captured so the harness records
an undo that recreates it. Pass dry_run=True to preview.

Args:
    name: Index name (optionally schema-qualified).
    concurrently: Drop with CONCURRENTLY (no table lock).
    dry_run: If True, preview without dropping.
    target: Target name from config; omit for the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
targetNo
dry_runNo
concurrentlyNo

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

With no annotations, the description fully discloses that this is a write operation with high risk, and importantly states it captures the index definition before dropping for reversibility. Also highlights dry_run for preview.

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 very concise, with a clear header, body explaining behavior, and a bullet list for parameters. Every sentence adds value with no filler.

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 no output schema and no annotations, the description covers the key aspects: purpose, risk, reversibility, and parameters. It could mention the return value or side effects more explicitly, but is sufficient for an experienced agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden. It explains each parameter: name (optionally schema-qualified), concurrently (no table lock), dry_run (preview), and target (config name). This adds significant meaning beyond the schema.

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 action 'Drop an index' with a [WRITE][risk=high] tag. It distinguishes this tool from siblings like create_index and reindex by specifying the exact operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the reversible nature and dry_run option, but does not explicitly contrast with alternatives. It clearly indicates when to use (to drop an index) but lacks when-not guidance.

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/AIops-tools/Postgres-AIops'

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