Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_postgres_schemas

Lists all schemas in a PostgreSQL database to reveal how tables are organized. Use it after listing databases to drill into a specific database's structure.

Instructions

List all schemas in a PostgreSQL database. Schemas organize tables within a database (e.g., 'public', 'analytics'). Use after list_postgres_databases to drill into a specific database.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_postgres_schemas"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseNoDatabase name (default: datris)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It makes clear this is a read-only listing and embeds it in a drill-down workflow, but it does not say what happens for an unknown database, whether the default database is used when the parameter is omitted, or what form results take. Adequate for a low-risk list tool, but not rich.

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?

Two sentences, zero waste: the purpose comes first, the workflow hint second. Each sentence earns its place and nothing is repeated from structured fields.

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?

For a one-optional-parameter listing tool with no annotations and no output schema, the description covers what it returns, the concept being listed, and its place in the sequence. Only edge-case behavior (missing database, default fallback) is unaddressed, which is minor at this complexity.

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% and the single optional 'database' parameter is documented in the schema, including its default of 'datris'. The description only implies the parameter through 'drill into a specific database' and adds no format or disambiguation detail beyond the schema; baseline 3 applies.

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?

Specific verb 'List' plus precise resource 'schemas in a PostgreSQL database'; the noun itself separates it from list_postgres_tables and list_postgres_databases. The brief gloss of what a schema is ('public', 'analytics') leaves no ambiguity about the returned entities.

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

Usage Guidelines4/5

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

Explicitly states the position in the workflow: 'Use after list_postgres_databases to drill into a specific database,' naming the predecessor sibling. It stops short of an explicit exclusion (e.g., 'use list_postgres_tables instead if you want tables'), so it is clear context rather than full when/when-not guidance.

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