Skip to main content
Glama
pg-perf-mcp

pg-perf-mcp

by dixitgurv

unused_indexes

Identifies non-unique PostgreSQL indexes unused since statistics were last reset, ordered largest first, to help review redundant indexes for removal.

Instructions

Non-unique indexes never used since stats were last reset, largest first.

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": "unused_indexes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does add real value by disclosing the critical caveat that results depend on when stats were last reset, plus the ordering ('largest first'). It does not state that the operation is read-only and safe, nor that a recently reset counter can make the list empty or misleading — a significant omission for a tool whose entire output validity hinges on that reset.

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?

One sentence, front-loaded with the filter condition and finished with the ordering. No filler, no restatement of the tool name.

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-field documentation is unnecessary. However, for a metrics-derived tool with zero annotations and an undocumented limit parameter, the description leaves the agent guessing about the meaning of 'largest' (index size vs. row count) and about how stats-reset staleness affects trustworthiness.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter (limit, default 20) is never mentioned in the description. The name is close to self-explanatory, but nothing clarifies whether limit truncates the largest-first list or whether it bounds scanning; the description does not compensate for the coverage gap.

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 names the resource precisely: non-unique indexes with zero usage since the last statistics reset, returned largest-first. That scoping ('non-unique', 'never used since stats were last reset') distinguishes it in substance from siblings like redundant_indexes, though it never names an alternative and omits an explicit verb such as 'list'.

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 statement of when to reach for this tool versus redundant_indexes, table_health, or database_overview, and no prerequisites or exclusions. The agent must infer that this is a cleanup-candidate discovery tool from the wording alone.

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