Skip to main content
Glama
pg-perf-mcp

pg-perf-mcp

by dixitgurv

redundant_indexes

Detect indexes whose columns are a leading prefix of another index on the same table, helping identify redundant PostgreSQL indexes that can be dropped to reduce write overhead and storage.

Instructions

Indexes whose columns are a leading prefix of another index on the same table.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "redundant_indexes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose the precise detection rule (leading-prefix overlap on the same table), which is real behavioral value, but it says nothing about scope (whole database vs. one table), whether it is read-only, or how overlap across multiple indexes is reported.

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?

A single tight sentence with no preamble or filler; the defining criterion is front-loaded and every word earns its place.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, but the definition gives no indication of scan scope or when to reach for it over unused_indexes. For a simple zero-parameter audit tool this is adequate yet leaves an obvious gap.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly introduces no phantom inputs.

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 defines the exact resource returned: indexes whose columns form a leading prefix of another index on the same table. That is a specific, diagnosable concept that distinguishes it from unused_indexes, though it is a noun phrase with no verb (list/find/return).

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to siblings such as unused_indexes or table_health. The agent must infer that this is a diagnostic tool to run when auditing index bloat or write overhead.

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