Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_get_compaction_status

Read-onlyIdempotent

Diagnose compaction lag by counting rowset versions per tablet and returning the top N tablets with the highest version accumulation.

Instructions

排查 compaction 落后:按 tablet 统计 rowset(版本)数量(information_schema.rowsets)。 单个 tablet 的 rowset 数持续偏高说明 compaction 跟不上写入。

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": "doris_get_compaction_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_nNo返回版本堆积最多的前 N 个 tablet

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds the underlying source (information_schema.rowsets) and a diagnostic interpretation hint, but it says nothing about the cost or breadth of scanning that view, the return shape, or rate limits.

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 sentences: the diagnostic goal and the data source come first, followed by the interpretation rule. There is no redundant or filler text.

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; annotations cover the safety profile; and the single parameter is fully documented. What remains is the interpretation guidance, which the description supplies.

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 the top_n parameter already documents itself as returning the top N tablets by rowset accumulation. The description adds no extra meaning about how top_n is applied, so the baseline 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 states a specific verb and resource: count rowset (version) numbers per tablet from information_schema.rowsets, framed as a compaction-lag diagnostic. It is clearly distinguishable from the sibling list/describe tools, though it does not explicitly compare itself to them.

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?

It gives a clear usage context (troubleshooting compaction falling behind writes) and an interpretation rule (a persistently high rowset count on one tablet means compaction cannot keep up). It does not name alternatives or state when NOT to use it, so it falls short of a 5.

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