Skip to main content
Glama
Huawei DCS MCP
by key-well

ListSlowlog

ListSlowlog
Read-onlyIdempotent

Query read-only slow logs for a Huawei DCS Redis instance by time range to diagnose performance issues, with optional node, sort, and pagination filters.

Instructions

查询慢日志(只读查询)

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": {
      "instance_id": "<instance_id>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "ListSlowlog"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNo查询节点,分为proxy和server。
limitNo每页显示的条目数量。
offsetNo偏移量,表示从此偏移量开始查询, offset大于等于0
regionNoOverrides HUAWEI_REGION.
end_timeYes查询结束时间,时间为UTC时间的Unix时间戳。如:1599494399000。
sort_dirNo降序或升序(分别对应desc和asc,默认为“desc”)
sort_keyNo返回结果按该关键字排序,支持start_time,duration,默认为“start_time”
project_idNoOverrides HUAWEI_PROJECT_ID.
start_timeYes查询开始时间,时间为UTC时间的Unix时间戳。如:1598803200000。
instance_idYes实例ID。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so "只读查询" merely restates structured data rather than adding context. Nothing is said about pagination behavior, result caps, whether the time window has a maximum span, or what the log entries contain. No contradiction with annotations, but almost no added behavioral value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short but under-specified rather than efficient: a two-word phrase plus a parenthetical that duplicates the readOnly annotation. There is no front-loaded statement of scope, required time range, or result shape because there is essentially no content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a ten-parameter paginated query tool with no output schema, the description leaves too much implicit: pagination semantics, sort defaults, the UTC-timestamp requirement, and the difference from sibling list tools are all left to the schema. The rich annotations cover the safety profile, but the description itself does not complete the picture.

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%, with every one of the ten parameters documented including defaults for sort_key and sort_dir. The description adds no meaning beyond that, 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?

"查询慢日志" names a specific verb (query) and resource (slow log), so an agent can tell what the tool returns without opening the schema. It does not distinguish itself from log-oriented siblings such as ListRedislog, 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?

The only guidance is the parenthetical "只读查询", which describes safety rather than when to call it. There is no statement of when this tool is appropriate versus ListRedislog or the Show* detail tools, and no note about required time-range or instance scoping.

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