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

ShowBandwidths

ShowBandwidths
Read-onlyIdempotent

Queries read-only shard bandwidth for a specified Huawei DCS Redis instance to help troubleshoot performance and capacity issues.

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

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
project_idNoOverrides HUAWEI_PROJECT_ID.
instance_idYes实例ID。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 the '只读查询' note merely restates structured data. The description adds no behavioral detail beyond the annotations, such as permission requirements, rate limits, whether results are per-shard, or what happens with region/project overrides. It does not contradict the annotations, but it also does not add context that the annotations already provide.

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?

The definition is a single front-loaded phrase with no filler, so an agent can parse it instantly. The only slight redundancy is the '(只读查询)' parenthetical, which repeats the readOnly annotation. Being terse is not penalized, but that duplication keeps it from a 5.

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

Completeness3/5

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

This is a simple read tool with one required parameter, full schema coverage, and no output schema, which means the description should explain what the bandwidth result contains (per shard? unit? current versus peak?). It omits that, and it omits whether any instance state is required. Adequate to invoke, but not complete enough to interpret the result confidently.

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 instance_id, region, and project_id are already documented in the input schema. The description contributes nothing about parameter meaning or format (for example, whether region/project_id override the environment defaults in practice). This meets the baseline 3 for a fully documented schema.

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 names a specific verb and resource: fetching shard bandwidth for an instance (获取实例分片带宽). That is concrete enough to separate it from siblings like ShowInstance, ShowNodesInformation, or ShowInstanceTopology, which cover different resources. It stops short of explicitly contrasting itself with any sibling, so a 4 rather than 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?

There is no guidance on when to use this tool versus alternatives, no prerequisites (for example, whether the instance must be running or have sharding enabled), and no exclusions. The parenthetical '只读查询' signals safety, not usage context, so the agent must infer the situation 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.