Retrieve load and performance statistics for a specific virtual machine using its ID. Monitor resource usage and health of your cloud VM.
Статистика виртуальной машины (vm/load_stats).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID виртуальной машины |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds the endpoint path 'vm/load_stats', which is mildly informative, but it does not disclose what statistics are returned, how they are scoped, or any operational caveats.
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?
The description is a single concise sentence that states the subject and includes the endpoint reference with no filler or redundant content. It is appropriately front-loaded and efficient.
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?
For a simple one-parameter read-only tool, the description is minimally adequate, but it lacks detail about the actual statistics returned, especially since no output schema exists. An agent would need additional context to interpret the response.
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?
The schema covers 100% of the parameter descriptions, including 'ID виртуальной машины'. The tool description adds no additional meaning beyond the schema, so 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource as a virtual machine and the operation as statistics retrieval, reinforced by the endpoint hint 'vm/load_stats'. It is not a tautology, though it lacks an explicit verb and does not explicitly distinguish itself from sibling tools.
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?
No guidance is provided about when to use this tool versus alternatives such as get_server_sensors, get_network_status, or get_port_graphs. The description gives no context, exclusions, or mention of better-suited sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.