Skip to main content
Glama
Sign In
postgres-dba-mcp

postgres-dba-mcp

by a-lafon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

list_objects

Read-only

Lists tables, views, sequences, or extensions in a specified schema. Use it to inspect PostgreSQL schema contents and identify database objects before running queries or planning changes.

Instructions

List objects in a schema

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": {
      "schema_name": "<schema_name>"
    },
    "name": "list_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_typeNoObject type: 'table', 'view', 'sequence', or 'extension'table
schema_nameYesSchema name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: it does not mention the default object_type=table behavior, ordering, or whether results are paginated or filtered by privileges.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, appropriate in size for a two-parameter read tool. It is efficient but borders on under-specified rather than concise.

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 simple read-only listing tool with full schema coverage and clear annotations, the definition is minimally adequate. It still omits the default-type caveat and any statement about result shape, which matters given there is no output schema.

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 description coverage is 100%, so both parameters are documented structurally, and the description's "in a schema" merely restates the schema_name scoping. The important subtlety—that omitting object_type silently defaults to tables only, hiding views/sequences/extensions—is left entirely to the schema's default field.

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?

"List objects in a schema" gives a verb and a resource, but "objects" is the vaguest possible term for what the enum actually exposes (table, view, sequence, extension). Nothing distinguishes it from siblings like get_object_details or list_schemas, so an agent must open the schema to learn what an "object" is here.

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 and no alternatives named. The sibling list contains list_schemas and get_object_details, which are obvious complements, yet the description gives no hint about choosing between discovering schemas, listing objects, or fetching details of one object.

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

Deploy Server

Other Tools