Run a read-only hcloud command through the toolkit safety policy and redact output.
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | Optional working directory for the hcloud process. | |
| args | Yes | ||
| timeoutMs | No | Optional timeout in milliseconds. Defaults to 60000. | |
| maxRetries | No | Optional retry count for transient network errors. Defaults to 1. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that output is redacted and that the command passes through a safety policy, which is useful behavioral context. With no annotations, more detail about failure modes or side-effect guarantees could strengthen transparency.
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?
One concise sentence conveys the main purpose and key behavioral constraints without redundancy or extraneous detail.
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?
Provides enough context for basic use: read-only scope, safety policy, and output redaction. Missing examples or edge-case guidance, but the tool is not highly complex and has no output schema to document.
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 essential 'args' parameter has no schema description and the tool description does not clarify its format or expected contents. Other parameters have basic descriptions, but the core required argument is underspecified.
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?
Description clearly states the tool runs a read-only hcloud command, identifying both the action and resource. The explicit 'read-only' qualifier distinguishes it from sibling tools like huaweicloud_run_approved_command.
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?
Provides clear context by limiting usage to read-only commands and mentioning the toolkit safety policy. Does not explicitly name alternative tools or state when not to use it, so it falls short of full explicit guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.