Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_postgres_tables

Lists all tables in a PostgreSQL schema, with an option to return only pgvector embedding tables. Use it after listing schemas to inspect available data or vector tables.

Instructions

List all tables in a PostgreSQL schema. Set vector_only=true to show only pgvector embedding tables, or false (default) to show regular data tables. Use after list_postgres_schemas.

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_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemaNoSchema name (default: public)
databaseNoDatabase name (default: datris)
vector_onlyNoIf true, only return tables with an embedding column (pgvector tables). Default: false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It implies a safe read and explains the pgvector filtering behavior, but says nothing about permissions, behavior on a nonexistent schema/database, or pagination limits for large schemas.

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?

Three short sentences, front-loaded with the core action, and no filler. The vector_only explanation mildly duplicates the schema description, which is the only waste.

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 simple read-only listing tool with zero required parameters and full schema coverage, the description covers purpose, sequencing, and the main filtering mode. The only gap is the absence of any hint about the return shape, since no output schema exists.

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%, so the schema already documents schema, database, and vector_only including defaults. The description restates the vector_only semantics ("embedding column (pgvector tables)") with essentially the same information, adding little beyond the structured fields.

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 opens with a specific verb and resource ("List all tables in a PostgreSQL schema") and immediately explains the vector_only variant, so an agent knows exactly what is returned. It does not explicitly contrast with siblings like list_postgres_columns, but the resource scope is unambiguous.

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?

"Use after list_postgres_schemas" gives concrete ordering guidance and the vector_only explanation tells the agent which mode to pick. There is no explicit when-not guidance or mention of sibling alternatives such as list_postgres_columns when column detail is needed.

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