Skip to main content
Glama
Sign In

Contabo (VPS) MCP Server

by ai.com.mcp
OverviewDiscussionsAdmin

Unassign a VIP to a VPS/VDS/Bare Metal

unassignIp
Destructive

Unassign a VIP to a VPS/VDS/Bare Metal - Unassign a VIP from an VPS/VDS/Bare Metal using the machine id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "x-request-id": "<x-request-id>",
      "resourceId": "<resourceId>",
      "ip": "<ip>",
      "resourceType": "<resourceType>"
    },
    "name": "unassignIp"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYes
resourceIdYes
x-trace-idNo
resourceTypeYes
x-request-idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / x-hapi-auth-state
      Removed value: -{
-  "type": "string"
-}
  2. First observed

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true. The description does not add any behavioral context beyond that, such as consequences of unassigning (e.g., losing IP connectivity) or requirements like the VIP being currently assigned.

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?

The description is repetitive, restating 'Unassign a VIP' twice in the same sentence, and contains grammatical errors ('an VPS'). The redundant phrasing could be condensed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive operation with 5 parameters and no output schema, the description is minimal. It omits side effects, required state, return behavior, and parameter details, leaving the agent under-informed.

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?

Schema has 0% description coverage, and the description only refers to 'machine id' (likely resourceId). It does not explain ip, resourceType, or the trace/request ID headers, leaving all parameters ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the operation: unassign a VIP from a VPS/VDS/Bare Metal using the machine id. It distinguishes from siblings like assignIp and unassignInstancePrivateNetwork. Although the title has a grammar error ('to' vs 'from'), the description corrects it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool instead of alternatives like assignIp or unassignInstancePrivateNetwork. It does not mention prerequisites or conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Contabo (VPS) MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources