Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_list_active_tasks

Read-onlyIdempotent

Lists currently executing queries in Apache Doris to monitor active tasks and identify when no queries are running.

Instructions

当前正在执行的查询(SHOW PROC '/current_queries',7 列)。空结果表示当前无活跃查询。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new context beyond that: the exact server command it wraps and the seven-column result shape, plus the meaning of an empty result, which is useful for interpreting output.

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, zero filler, with the resource identity front-loaded and the empty-result caveat second. Every clause carries information an agent can act on.

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 need not explain return values, and it still adds the column count and empty-result semantics. For a zero-parameter read-only monitoring tool this is essentially complete, with only the lack of sibling routing as a minor gap.

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?

The tool takes no parameters, so the schema has nothing to document and no semantic burden falls on the description. Baseline 4 applies; the description appropriately says nothing about inputs.

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 resource and state — '当前正在执行的查询' — and names the underlying mechanism (SHOW PROC '/current_queries'), so an agent knows exactly what it retrieves. It is clearly distinct from catalog/table listing or profile-fetching siblings, though it does not explicitly contrast itself with any of them by name.

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: the agent can infer this is the tool for inspecting in-flight work, and the note that an empty result means no active queries clarifies the diagnostic reading. However, there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as the query-profile or cluster-overview tools for deeper investigation.

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