Skip to main content
Glama
pg-perf-mcp

pg-perf-mcp

by dixitgurv

database_overview

Retrieve a PostgreSQL health snapshot covering cache hit rate, temp file usage, deadlocks, key memory settings, and connection counts to spot configuration and resource issues quickly.

Instructions

Cache hit rate, temp file usage, deadlocks, key memory settings and connection count.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it says nothing about this being a read-only operation, whether it requires elevated privileges (deadlock and memory counters often do), or the cost of sampling server state. It only enumerates the metrics, leaving the safety and side-effect profile unstated.

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

Conciseness3/5

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

It is a single short sentence with no waste, but it is a fragment with no leading verb, so the reader must infer the action from the tool name. Brevity is bought at the cost of front-loading an actual purpose.

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 the metrics need not be re-explained, and with zero parameters the schema demands nothing. For a simple no-arg diagnostic tool the definition is nearly sufficient, but the missing indication of when to call it and what kind of read it is leaves a real 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 semantics to explain and the baseline of 4 applies. The description neither helps nor hurts here.

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

Purpose3/5

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

The description is a noun phrase listing metrics ('cache hit rate, temp file usage, deadlocks, key memory settings and connection count') rather than a verb-plus-resource statement of what the tool does. It is more informative than a tautology and implies server-level health reporting, which implicitly contrasts with the query/index-focused siblings, but it never says it returns an overview snapshot.

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 exclusions, and no reference to any alternative. An agent cannot tell from this text whether to reach for database_overview or slow_queries when investigating performance, even though those are the most plausible competing choices.

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