Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_list_tables

Read-onlyIdempotent

List tables and views in a Doris database with pagination, returning names, types, and total counts. Filter by name pattern and paging to browse schemas quickly.

Instructions

列出某个库下的表,分页返回,并区分表与视图。

    internal:走 information_schema.tables(1.2 的 SHOW TABLES 不支持 LIMIT),
    WHERE TABLE_SCHEMA + 可选 LIKE 在服务端过滤;其他 catalog 用 SHOW TABLES FROM,
    取回后本地切页。

    返回:{ok, total, count, offset, limit, items[{name, type}], has_more, next_offset, source}
    

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": {
      "database": "<database>"
    },
    "name": "doris_list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo本页返回条数
offsetNo跳过条数,用于翻页
catalogNo可选,catalog 名;默认 internal
databaseYes数据库名
name_likeNo可选,表名 LIKE 模式,如 ods_%

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare it as a safe, read-only, idempotent operation. The description adds meaningful behavioral context: server-side filtering for internal catalog (with the 1.2 SHOW TABLES LIMIT workaround) versus local pagination for other catalogs, and includes a detailed return shape.

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?

The description is front-loaded with the core purpose, then provides implementation details in a structured way. It is dense but every sentence adds useful information; no unnecessary repetition.

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?

Given the output schema exists, the return shape is redundant but helpful. The description covers catalog-specific behavior and pagination, which are key for correct invocation. Minor gaps include error handling and permission requirements, but overall it is complete for a listing tool.

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

Parameters4/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 each parameter. The description adds value by clarifying that name_like performs server-side LIKE filtering for the internal catalog and that pagination behavior differs by catalog, beyond what the schema states.

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 states a specific verb (列出/list) and resource (某个库下的表/tables under a database), and adds scope details like pagination and distinguishing tables from views. No sibling tool performs the same function, so it is clearly differentiated.

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 implied: use this to list tables in a database. However, it does not explicitly say when to use this versus alternatives like doris_describe_table or doris_execute_query, nor does it provide exclusions or prerequisites.

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