Skip to main content
Glama
Sign In
drill-mcp

drill-mcp

Official
by apache
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_tables

Retrieve all tables in a specified schema for quick database structure inspection.

Instructions

List the tables in one schema.

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": {
      "schema": "<schema>"
    },
    "name": "list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemaYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 burden of behavioral disclosure. It only states the operation is 'List', implying read-only behavior, but does not mention permissions, whether views are included, output format, or any side effects. This is minimal transparency.

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?

The description is a single, simple sentence with no redundant information. It is appropriately front-loaded and achieves maximum conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description lacks essential contextual information: it does not differentiate from list_schemas, specify if the schema must be pre-existing, or mention whether the result includes only user-defined tables. Given the sparse sibling context, this is insufficient for reliable tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, and the description does not compensate. While the text mentions 'one schema', it does not explain the expected format, whether it is a schema name or identifier, or any constraints. This adds barely more meaning than the schema property title '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?

The description clearly states the tool's purpose: 'List the tables in one schema.' The verb 'List' identifies a read operation on a specific resource ('tables'), and 'in one schema' clarifies the scope. This differentiates it from sibling tools like list_schemas (which lists schemas) and describe_table (which describes a single table).

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?

The description offers no guidance on when to use this tool versus alternatives such as list_schemas, describe_table, or run_query. It does not mention prerequisites (e.g., the schema must exist) or any exclusions. The only implied usage is that it returns tables for a given schema, which is not enough for informed selection.

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