Skip to main content
Glama
multidb-mcp

multidb-mcp

list_tables

Lists all tables in a target database schema, using the default schema and connection when omitted, so you can inspect available tables before querying.

Instructions

List all tables in a schema of the target 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 to list tables from. Uses the connection default if omitted.
connectionNoConnection name. Omit when only one is configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden, yet 'List' is the only indicator that this is a read-only operation. It does not state what happens with an invalid or missing schema, whether it errors or returns empty, whether permissions are required, or how large the result may be.

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?

It is a single front-loaded sentence with no filler or redundancy. Its brevity is efficient rather than padded, though the same brevity is the source of the gaps scored elsewhere.

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?

For a two-parameter, zero-required read tool this is close to adequate, and the schema documents both parameters well. However, with no output schema and no annotations, the description should at least indicate what is returned (bare table names vs. qualified names or metadata) to let an agent use the result correctly.

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 both parameters already document their fallback behavior (default schema, default connection) in the input schema. The description mentions schema and database context but adds no meaning beyond what the schema already states, so the baseline of 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?

The description gives a specific verb and resource ("List all tables") scoped to a schema of the target database, which an agent can easily distinguish from siblings like describe_table or execute_sql. It stops short of explicitly naming how it differs from those siblings, but the operation itself 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 Guidelines2/5

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

There is no when-to-use guidance: nothing says to call this before describe_table, or that a connection must be established first (a real concern given list_connections and test_connection are siblings). Usage is only inferable from the tool name, not stated in the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.