Retrieve the current state, IP addresses, region, and type of any managed server instance. Provide an instance ID, name, or custom-server name to inspect its status.
Check status of any managed instance (state, IPs, region, type).
| Name | Required | Description | Default |
|---|---|---|---|
| instance_id | Yes | Instance ID, name, or custom-server name. |
Changes observed during successful MCP inspections.
v2.24.0v2.23.8v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full behavioral disclosure burden. It implies a read operation ('Check status') but does not explicitly state it is read-only, non-destructive, or what side effects exist. Minimal behavioral context.
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 sentence of 12 words, very concise and front-loaded with the verb 'Check status'. It wastes no words, but could potentially include a tiny bit more context without losing conciseness.
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?
Given no output schema or annotations, the description covers the basic purpose and output fields. However, it lacks usage context, differentiation from siblings, and behavioral details. It is adequate but has clear gaps.
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 input schema already has 100% coverage with a clear parameter description. The description adds no new parameter semantics beyond the schema, but it clarifies the output fields (state, IPs, region, type), which indirectly helps agents understand what they will get. 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 states the tool checks status of a managed instance and lists fields like state, IPs, region, type. However, it does not differentiate from sibling tool 'get_server_info', which likely returns similar information, so sibling differentiation is missing.
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 usage guidance is provided. There is no indication of when to use this tool versus alternatives like 'get_server_info' or 'list_instances'. No when-not-to-use or prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.