Rank the top five servers by CPU, memory, or filesystem usage from Cloud Insight monitoring to identify high-utilization instances.
Get the top 5 servers by CPU, memory, or filesystem usage from Cloud Insight monitoring.
| Name | Required | Description | Default |
|---|---|---|---|
| prod | No | Server environment: VPC (default) or Classic | |
| query | Yes | Metric to rank by: avg_cpu_used_rto (CPU), mem_usert (memory), avg_fs_usert (filesystem) |
Changes observed during successful MCP inspections.
v2.0.1Input schema / properties / metricTypeRemoved value: -{
- "description": "Metric type to rank servers by (cpu, memory, or fs)",
- "enum": [
- "cpu",
- "memory",
- "fs"
- ],
- "type": "string"
-}Input schema / properties / prodAdded value: +{
+ "description": "Server environment: VPC (default) or Classic",
+ "enum": [
+ "VPC",
+ "Classic"
+ ],
+ "type": "string"
+}Input schema / properties / queryAdded value: +{
+ "description": "Metric to rank by: avg_cpu_used_rto (CPU), mem_usert (memory), avg_fs_usert (filesystem)",
+ "enum": [
+ "avg_cpu_used_rto",
+ "mem_usert",
+ "avg_fs_usert"
+ ],
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "metricType"
-]New value: +[
+ "query"
+]v1.10.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true already tells the agent this is a safe read. The description adds two useful behavioral facts: the output is capped at 5 entries and the data originates from Cloud Insight monitoring. It does not state the observation time window (and no time parameter exists), so the agent cannot infer how the ranking is computed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with the resource, the fixed cardinality, and the ranking dimension. No filler, no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The parameters are fully covered by the schema and there is no output schema, so return-value detail is not strictly required. However, for a monitoring query the description omits the time/aggregation window used for ranking and the shape of the result, both of which an agent would want before relying on the output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and both parameters are enums, each with a schema-level description. The description's 'CPU, memory, or filesystem usage' merely restates the query enum meanings already documented in the schema, adding no format or default detail beyond it, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a concrete verb and resource: 'Get the top 5 servers by CPU, memory, or filesystem usage', plus the source system (Cloud Insight monitoring). It clearly implies this is a bounded top-N ranking rather than a full server list, which separates it in spirit from ncloud_list_servers, though it never names an alternative tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It names the three metrics you can rank by, which implies when to reach for this tool (metric-based ranking), but there is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no routing to or away from alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.