Skip to main content
Glama
Sign In
pii-safe-db-mcp

pii-safe-db-mcp

by aqibsidd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List tables

list_tables
Read-only

Lists tables and views in the connected PostgreSQL database, optionally filtered by schema, to help discover available data structures before running read-only queries.

Instructions

List tables and views in the connected postgres 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_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemaNoSchema/database name. Defaults to the current one.

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?

readOnlyHint already declares the safety profile, so the description's contribution is limited. It does add two useful facts beyond the annotation: the result includes views, not just tables, and the scope is the connected database. It says nothing about result shape or ordering, which with no output schema is a real gap.

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?

A single twelve-word sentence with zero filler, front-loaded with the verb. Nothing could be removed without losing information.

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 zero-required-parameter, read-only listing tool with annotations covering safety and full schema coverage, this is nearly complete. The only missing piece is a hint about what each returned row contains, which matters because 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% and the single optional 'schema' parameter is fully documented in the schema, including its default. The description adds no param meaning beyond that, so baseline 3 applies.

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?

States a specific verb and resource ('List tables and views') scoped to the connected postgres database. It implicitly distinguishes from describe_table and query by being the enumeration operation, though it never names those siblings.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the discovery step before describe_table or query. There is no explicit when-to-use, when-not-to-use, or reference to the sibling tools that operate on the objects it lists.

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