Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_get_table_partitions

Read-onlyIdempotent

Lists a Doris table's partitions and their latest visible version times so you can check partition coverage and measure data freshness lag.

Instructions

看分区清单与数据新鲜度(SHOW PARTITIONS,17 列)。 VisibleVersionTime 是分区最新可见版本时间,用它算滞后(官方 monitor_data_freshness)。

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

Input Schema

NameRequiredDescriptionDefault
tableYes表名
databaseYes数据库名

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/ idempotent annotations, it discloses that the call maps to SHOW PARTITIONS, that the result has 17 columns, and that VisibleVersionTime is the field to use for freshness lag — useful semantics the agent could not get from annotations alone. It still doesn't mention cost, row limits, or behavior on non-partitioned tables, but the annotation baseline already covers safety.

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 short lines, front-loaded with the purpose and followed by the one non-obvious detail (which column drives freshness). No filler, no repetition of name or annotation facts.

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?

With an output schema present, the description needn't explain return values, and it still highlights the 17-column shape and the key column for the stated freshness use case. Remaining gaps — result size on large partitioned tables and whether it requires ADMIN privileges — are minor for a read-only inspection tool.

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 description coverage is 100% and both parameters (database, table) are documented in the schema, so the schema carries the burden. The description adds no per-parameter detail such as what happens when the table is not partitioned or whether database is the catalog-level name.

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 ('看分区清单' - view partition list) plus a secondary purpose ('数据新鲜度' - data freshness), and names the underlying command SHOW PARTITIONS. The resource (partitions of a table) is distinct from siblings like doris_get_table_size or doris_describe_table, though the description never explicitly contrasts itself with them.

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 rather than stated: '用它算滞后' (use it to compute lag) tells the agent this is the right tool for freshness checks, and the reference to 官方 monitor_data_freshness points at the intended analysis. There is no explicit when-not guidance or comparison to alternatives such as doris_get_table_size.

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