Skip to main content
Glama
Sign In
AlibabaCloud MCP Server

AlibabaCloud MCP Server

Official
by aliyun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

GetCpuUsageData

Monitor and retrieve CPU usage data for AlibabaCloud ECS instances by specifying region and instance IDs, enabling efficient resource management and performance tracking.

Instructions

获取ECS实例的CPU使用率数据

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": {
      "InstanceIds": "<InstanceIds>"
    },
    "name": "GetCpuUsageData"
  }
}

Input Schema

NameRequiredDescriptionDefault
InstanceIdsYesAlibabaCloud ECS instance ID List
RegionIdNoAlibabaCloud region IDcn-hangzhou

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states '获取' (get), implying a read-only operation, but doesn't clarify aspects like authentication requirements, rate limits, data freshness, or response format. For a tool with no annotations, this leaves significant behavioral gaps.

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?

The description is a single, efficient sentence in Chinese that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given no annotations, no output schema, and a read operation with potential complexity (e.g., data aggregation, time ranges), the description is incomplete. It lacks details on return values, error handling, or operational context, making it inadequate for full agent understanding without external inference.

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 clear descriptions for both parameters (InstanceIds and RegionId). The description adds no additional parameter semantics beyond what the schema provides, such as format details or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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 clearly states the verb ('获取' meaning 'get') and resource ('ECS实例的CPU使用率数据' meaning 'ECS instance CPU usage data'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like GetCpuloadavgData or GetMemUsageData, which target different metrics, leaving some ambiguity about when to choose this specific CPU metric tool.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like GetCpuloadavgData (for load averages) or GetMemUsageData (for memory), nor does it specify prerequisites, contexts, or exclusions for usage, leaving the agent to infer based on tool names alone.

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

Deploy Server

Other Tools

Related Tools