Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_get_ingestion_status

Read-onlyIdempotent

Retrieve recent Doris ingestion status for Broker one-time loads and routine loads, optionally scoped to a database, to monitor load health and troubleshoot failures.

Instructions

导入任务状态:SHOW LOAD(17 列,Broker/Routine 一次性导入)与 SHOW ROUTINE LOAD(19 列,常驻例行导入)。默认两类都给。

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

Input Schema

NameRequiredDescriptionDefault
kindNoall(默认)/ load / routine_loadall
limitNo每类返回的最近任务数
databaseNo可选,库上下文;SHOW LOAD / SHOW ROUTINE LOAD 需要连接已选库

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds that SHOW LOAD covers one-time Broker/Routine loads and SHOW ROUTINE LOAD covers persistent loads, and that both are returned by default, but it omits auth, pagination, and scoping caveats.

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?

Two short sentences, front-loaded with the purpose and default behavior. The column counts (17/19) are marginally useful and there is no filler; the definition is very concise.

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?

For a simple read-only status tool with a fully described 3-parameter schema, rich annotations, and an output schema, the definition covers the essential modes and default. It could be stronger with database-connection or sibling-routing guidance, but nothing critical is missing.

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%, so the schema already documents kind, limit, and database. The description clarifies that kind=load maps to SHOW LOAD and kind=routine_load maps to SHOW ROUTINE LOAD, but otherwise adds little beyond the schema's enum labels.

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?

Names the specific resource (ingestion task status) and the two Doris commands it wraps, SHOW LOAD and SHOW ROUTINE LOAD, distinguishing one-time Broker/Routine loads from persistent routine loads. It does not differentiate from sibling status tools, so it stops short of a 5.

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?

States the default behavior of returning both kinds, but gives no explicit when-to-use guidance, no when-not conditions, and no alternatives such as active-task or compaction status tools. An agent must infer usage from the tool name.

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