hcloud_show_scaling_groupRetrieve detailed information about a specific Auto Scaling group by region and scaling group ID, so you can inspect its configuration and properties.
Get details of a specific AS group
| Name | Required | Description | Default |
|---|---|---|---|
| region | Yes | Region | |
| scaling_group_id | Yes | Scaling group ID |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description contributes nothing further: no note on error behavior for unknown IDs, cross-region lookup behavior, or what level of detail is returned.
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 no filler. It is efficient, though its brevity is closer to under-specification than to disciplined concision.
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 read-only lookup with full schema coverage and annotations, the essentials are present. Gaps remain around region/ID interaction and the shape of the returned detail, which the absent output schema leaves unexplained.
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 coverage is 100%, so both parameters are documented in the schema, making 3 the baseline. The description adds no meaning beyond them, notably not explaining why a region is required alongside a globally unique scaling group ID.
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 gives a specific verb ("Get details") and a specific resource ("a specific AS group"), which is enough to distinguish it from the listing sibling hcloud_list_scaling_groups. It does not name that sibling or expand "AS", so a bit of inference is required.
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?
Usage is only implied: fetch one group by ID rather than enumerate them. There is no explicit statement of when to prefer this over hcloud_list_scaling_groups, nor any precondition such as obtaining the ID from the list call first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.