Set default handle
setDefaultHandleDestructive
Set default handle - Set default handle
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| handleId | Yes | ||
| x-trace-id | No | ||
| x-request-id | Yes |
Contabo (VPS) MCP Server
by ai.com.mcp
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Changed1 schema field changed
- removed
Input schema / properties / x-hapi-auth-stateRemoved value: -{ - "type": "string" -}
- First observed
TDQS
D1.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=false and destructiveHint=true, and the description does not contradict these. However, the description adds no behavioral context whatsoever—it does not explain what changes occur, whether the operation is reversible, or what side effects exist. It provides no additional transparency beyond the existing annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
While the description is short, it is under-specified and redundant. It repeats the title instead of providing useful structure or front-loaded key information. The single sentence fails to earn its place as a helpful description, offering no value to the reader.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, no parameter explanations, and no usage guidance, the description is completely inadequate. The tool likely performs a state-changing operation (setting a default), but the agent has no idea what handleId refers to, what request IDs are needed, or what the outcome will be. This is insufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 3 parameters with 0% description coverage, and the description does not explain any of them. handleId, x-request-id, and x-trace-id are left entirely undocumented, so the agent has no semantic guidance for providing correct values or understanding their purpose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Set default handle - Set default handle' is a tautology that merely restates the tool name/title. It does not specify what setting a default handle entails, what a 'handle' refers to, or what action is actually performed. This provides no informative content to distinguish it from other handle-related tools like createHandle or updateHandle.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives such as createHandle, updateHandle, or removeHandle. There is no mention of prerequisites, context, or exclusions, leaving the agent without any direction for selecting this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.2/5.0
Disambiguation2/5
Many tools have clearly distinct CRUD roles per resource, but there are several confusing overlaps: start/stop/restart/shutdown/rescue are similar lifecycle actions, and there are duplicate audit tools like retrieveImageAuditsList and retrieveImageAuditsList1 (one even mislabeled as DNS Zones audit). Additionally, retrieveTagAuditsList appears to duplicate retrieveAssignmentsAuditsList, and updateDnsZoneRecord incorrectly says 'Create resource record'. These overlaps and mislabeled descriptions make it hard to pick the right tool.
Naming Consistency2/5
The naming is a mix of camelCase verb_noun patterns, but inconsistent. Some tools use 'retrieveXList' while others use 'listX', some use 'Cancel' with a capital letter, and 'tool_search' uses snake_case. Numeric suffixes like 'retrieveImageAuditsList1' and verbs like 'patchInstance' instead of 'updateInstance' further break consistency.
Tool Count1/5
With 124 tools, this is an extremely large tool surface for an MCP server. Even for a broad cloud provider API, this overwhelms an agent's context and selection capabilities. The number far exceeds reasonable scoping and creates unnecessary selection overhead.
Completeness4/5
The tool set covers a wide range of resources thoroughly: instances, snapshots, images, private networks, object storage, DNS, domains, tags, roles, users, secrets, and audits. Most resources have create/retrieve/update/delete lifecycle operations, and there are extensive audit history tools. Minor gaps exist (e.g., no explicit instance deletion besides cancel, no separate firewall management beyond upgradeInstance), but overall the surface is quite complete for its domain.