Skip to main content
Glama

Table stats

table_stats

Retrieve live/dead row counts, sequential versus index scan counts, and table/index sizes for a PostgreSQL table to assess performance and maintenance needs.

Instructions

Statistics for one table: live/dead rows, sequential vs index scan counts, and table/index sizes.

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

NameRequiredDescriptionDefault
tableYesTable name, e.g. "orders".
schemaNoSchema name. Defaults to "public".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does signal a read-only, single-table scope and discloses the shape of the result, which is valuable since there is no output schema. It says nothing about stat freshness (e.g. whether values reflect the last ANALYZE), permissions, or whether counters are cumulative since the last 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?

A single front-loaded sentence that enumerates the returned metrics with zero filler. Every clause adds information an agent can act on.

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?

For a two-parameter read tool with no annotations and no output schema, the description does the minimum useful work by naming the metrics returned. It is still incomplete on stat freshness, whether scan counts are cumulative, and how this differs from describe_table.

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 100% and both parameters (table, schema) are documented in the schema, including the 'public' default, so the description adds no parameter meaning beyond it. Baseline 3 applies; 'for one table' only restates the required parameter.

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?

Names the resource (one table) and enumerates the concrete metrics returned: live/dead rows, sequential vs index scan counts, table/index sizes. That is far more specific than the title. It does not, however, distinguish itself from the sibling describe_table, which an agent could easily confuse with a stats tool.

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?

No when-to-use guidance at all: nothing says to prefer this over describe_table for sizing/scan analysis, or to use suggest_indexes when the scan counts suggest a problem. The agent must infer the trigger condition from the metric list alone.

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