List dedicated-server vSwitches on Hetzner Robot or fetch one by ID, with optional name/label filters and verbose output.
List vSwitches. Read only.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Fetch one by id. | |
| query | No | Filters, e.g. name, label_selector. | |
| verbose | No | Full payload. |
Changes observed during successful MCP inspections.
v0.7.0Input schema / properties / id / descriptionPrevious value: -"Optional resource id to fetch a single item."New value: +"Fetch one by id."Input schema / properties / query / additionalProperties / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "number"
- },
- {
- "type": "boolean"
- }
-]Input schema / properties / query / additionalProperties / typeAdded value: +[
+ "string",
+ "number",
+ "boolean"
+]Input schema / properties / query / descriptionPrevious value: -"Optional query parameters such as name or label_selector."New value: +"Filters, e.g. name, label_selector."Input schema / properties / verbose / descriptionPrevious value: -"Return full payload instead of the compact view."New value: +"Full payload."v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Read only' is the sole behavioral claim and it is thin: nothing is said about pagination, filtering semantics, auth requirements, or result size even though the 'query' and 'verbose' params imply variable output.
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?
Two short fragments with zero filler, front-loading the core action. It is efficient, though bordering on under-specification rather than true 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?
With three parameters, one a nested filter object, and no output schema, the description should at least hint at filtering/return shape. Instead it leaves all of that to the schema, which is thin given the nested 'query' object.
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%, so the schema already documents id, query, and verbose; the baseline of 3 applies. The description adds nothing about how 'query' filters interact or what 'verbose' expands, so it does not exceed the schema.
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 names a specific verb and resource ('List vSwitches'), so an agent knows exactly what is returned. There are no sibling vSwitch tools to differentiate from, but it is otherwise crisp and unambiguous.
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?
There is no when-to-use guidance, no mention of alternatives (e.g. other robot_list_* tools), and no prerequisites. 'Read only' restates safety rather than telling the agent when this tool is the right choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.