Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_postgres_columns

Lists all columns and data types for a PostgreSQL table so you can understand its structure before writing SQL queries.

Instructions

List all columns and their data types for a specific PostgreSQL table. Use this to understand table structure before writing a query_postgres SQL query.

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": {
      "table": "<table>"
    },
    "name": "list_postgres_columns"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name
schemaNoSchema name (default: public)
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?

With no annotations, the description carries the burden. 'List' implies a safe read and the description discloses what is returned (columns plus data types), but says nothing about output volume, pagination, or behavior for a nonexistent table or schema.

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, no filler, with the core capability front-loaded ahead of the usage hint. Every sentence earns its place.

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 three-parameter read tool with no output schema, the description conveys both what is returned and when to call it. Only edge-case behavior (missing table, cross-database lookup) is left unstated.

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 table, schema, and database including defaults. The description only reinforces that the table is 'specific' and adds no format or qualification details beyond the schema.

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?

States a specific verb ('List'), resource ('columns and their data types'), and scope ('for a specific PostgreSQL table'). This is unambiguous and clearly distinct from query_postgres, which executes SQL rather than describing structure.

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 names the when and the follow-up: use it to understand table structure before writing a query_postgres SQL query. It gives no explicit exclusion conditions (e.g., when to prefer list_postgres_tables first), but the sequencing guidance is concrete.

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