postgres-mcp

table_stats

Retrieve size and activity statistics for a PostgreSQL table, including live and dead rows, table sizes, last vacuum and analyze times, and scan ratios.

Instructions

Size and activity statistics for a table (live/dead rows, sizes, last vacuum/analyze, sequential vs index scans).

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": {
      "table": "<table>"
    },
    "name": "table_stats"
  }
}

Input Schema

Name	Required	Description	Default
`table`	Yes
`schema`	No		public

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Description discloses types of statistics returned (live/dead rows, sizes, last vacuum/analyze, scans). No mention of it being read-only or side-effect-free, but output schema exists. Good behavioral context beyond what schema provides.

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?

Single sentence with examples in parentheses, no wasted words. Front-loaded with 'Size and activity statistics'.

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?

Output schema exists so return values need not be described. Description complements by listing statistics categories. Parameters are simple; no missing context for normal usage.

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 coverage is 0% but parameters are self-explanatory (table, schema). Description does not add parameter details; baseline of 3 is appropriate as schema names carry meaning.

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?

Description clearly states the tool returns size and activity statistics for a specific table, listing examples. It distinguishes from siblings which are about listing schema objects or running queries.

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

Usage Guidelines3/5

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

No explicit guidance on when to use or alternatives, but the purpose is clear enough that an agent can infer usage from the context of database tools.

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

Deploy Server