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

ListRedislog

ListRedislog
Read-onlyIdempotent

Retrieves a paginated list of Redis run logs for a specified cloud Redis instance, enabling read-only troubleshooting without executing Redis commands.

Instructions

查询Redis运行日志列表(只读查询)

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>",
      "log_type": "<log_type>"
    },
    "name": "ListRedislog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo每页显示的条目数量。
offsetNo偏移量,表示从此偏移量开始查询, offset大于等于0
regionNoOverrides HUAWEI_REGION.
log_typeYes返回日志的类型,当前仅支持Redis运行日志,类型为run
project_idNoOverrides HUAWEI_PROJECT_ID.
instance_idYes实例ID。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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, and the description's '(只读查询)' merely restates that. It adds nothing about pagination behavior, what a log entry contains, retention windows, or the fact that log_type currently only accepts 'run'.

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

Conciseness3/5

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

It is a single short sentence that is front-loaded with the core action, so nothing is buried. However, the parenthetical is redundant with the annotations, and the brevity reflects under-specification rather than disciplined editing.

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 six-parameter list tool with no output schema, the description says nothing about the shape of returned log entries, default/maximum page size, or ordering. It leans entirely on the schema and annotations, leaving behavioral questions an agent would have before calling it unanswered.

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 every parameter (instance_id, log_type, limit, offset, region, project_id) is already documented in the schema. The description adds no additional meaning about parameter interaction, such as default page size or how region/project_id override environment settings, 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 ('查询Redis运行日志列表' — query the Redis runtime log list), which is unambiguous about what the tool returns. It does not, however, distinguish itself from close siblings such as ListSlowlog, which an agent could easily confuse with runtime logs.

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?

There is no guidance on when to use this tool versus alternatives — most notably ListSlowlog, the other log-listing sibling. The only contextual note, '(只读查询)', describes safety rather than selection criteria, so the agent must infer usage from the name alone.

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