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

postgres-dba-mcp

by a-lafon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

get_object_details

Read-only

Retrieve detailed metadata for a PostgreSQL table, view, sequence, or extension by schema and object name to inspect structure and properties.

Instructions

Show detailed information about a database object

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>",
      "object_name": "<object_name>"
    },
    "name": "get_object_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_nameYesObject name
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.9/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 covered. The description adds nothing beyond that — no note on what happens when the object is missing, how object_type affects the result shape, or any cost/latency characteristics. With annotations doing all the work, the description contributes little.

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 short sentence with the verb front-loaded and zero filler. It is efficient, though its brevity edges toward under-specification rather than genuine conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining what "detailed information" actually contains, and it says nothing about the fields returned or how they differ across table/view/sequence/extension. For a lookup tool whose whole value is the shape of its return payload, this is a material gap.

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%, including an enum for object_type, so the schema fully documents all three parameters. The description adds no extra meaning about how schema_name or object_type influence the returned detail, which is the baseline expectation when the schema is this complete.

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 gives a specific verb and resource ("Show detailed information about a database object"), which is clear enough for an agent to understand the operation. However, it does not distinguish this from sibling tools like list_objects, leaving the agent to infer that this one returns per-object details rather than a listing.

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 guidance on when to use this tool versus list_objects or execute_sql, and no stated prerequisites such as the object needing to already exist. The only hint is the tool name itself, which is not part of the description text.

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