Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_get_table_size

Read-onlyIdempotent

Retrieve storage size for a Doris database or table; when a table is specified, return total data bytes and partition count.

Instructions

看表/库的数据量。不传 table:SHOW DATA(必须先选库,返回每表 Size + ReplicaCount)。 传 table:SHOW PARTITIONS 汇总 DataSize,给出总字节数与分区数。

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_get_table_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableNo可选,表名;不传则返回该库所有表的大小
databaseYes数据库名

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes further by naming the underlying statements (SHOW DATA vs SHOW PARTITIONS), disclosing the prerequisite that a database must be selected first, and stating what each mode returns (Size + ReplicaCount, or total bytes + partition count). It does not discuss cost, latency, or permissions, which would be the remaining behavioral gaps.

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 purpose is front-loaded and the two branches are presented in a compact parallel structure with no filler sentences. The multi-line layout is slightly ragged but every clause carries 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?

An output schema exists, so return values need not be explained, and the description still covers both invocation modes and the ordering prerequisite. Only cross-tool routing against similar introspection siblings is absent, which keeps it short of a 5.

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 baseline is 3, and the description earns a point by contrasting what the two states of the optional `table` parameter actually produce rather than just restating that it is optional. It adds more than the schema, though the underlying SQL detail is close to duplicating the parameter's documented meaning.

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 names a specific verb and resource (data volume of a table or database) and spells out two distinct operating modes. It does not, however, distinguish itself from the sibling doris_get_table_partitions, which the 'table passed' mode (SHOW PARTITIONS) partially overlaps with, so the boundary is left implicit.

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

Usage Guidelines4/5

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

Clear conditional guidance: omit `table` to get per-table size for a database, pass `table` to get aggregated partition data. What is missing is routing advice against related siblings such as doris_get_table_partitions or doris_list_tables, and the description does not say when this tool should not be used.

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