Skip to main content
Glama
Sign In
pg-mcp

pg-mcp

by andre-c-andersen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_schemas

Lists all schemas in a PostgreSQL database using a specified connection name.

Instructions

List all schemas in the database

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": {
      "conn_name": "<conn_name>"
    },
    "name": "list_schemas"
  }
}

Input Schema

NameRequiredDescriptionDefault
conn_nameYesConnection name - see server instructions for available connections

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose all behavioral traits. It only states the action 'list all schemas' without mentioning limitations (e.g., pagination, performance, read-only nature) or return format. The description is insufficient for understanding the tool's full behavior.

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?

The description is a single, succinct sentence that immediately conveys the tool's purpose. There is no unnecessary information, and it is well-structured for quick comprehension.

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?

Given the tool's simplicity (single parameter, no output schema, no annotations), the description provides the essential action. However, it lacks context about the return value (e.g., list of schema names) and the specific database scope. It is minimally adequate but could be more informative.

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% (one parameter described). The tool description adds no additional meaning beyond the schema's 'Connection name - see server instructions for available connections'. Per guidelines, baseline is 3 for high coverage, and no extra value is provided.

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 'List all schemas in the database' clearly states the verb 'List' and resource 'schemas'. It is distinct from sibling tools like 'execute_sql' (execute queries) and 'list_objects' (list objects within a schema). However, it does not specify which database or connection context, though the input schema implies it.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., need to have a connection established) or when not to use it. Sibling tools are not referenced.

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