Skip to main content
Glama

Delete VPS SSH key

vps_delete_ssh_key
Destructive

Delete an SSH key from a VPS. If it was the web terminal key, the terminal key is cleared. Destructive: requires confirm=true.

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": {
      "id": "<id>",
      "keyId": "<keyId>",
      "confirm": "<confirm>"
    },
    "name": "vps_delete_ssh_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
keyIdYesThe key ID to delete
confirmYesMust be true to confirm this destructive operation

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark this destructive and non-read-only, and the description adds real context beyond them: the non-obvious side effect that deleting the web terminal key also clears the terminal key, plus the mandatory confirm=true gate. It does not describe error conditions or irreversibility of the key material, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the action, followed by the side effect and then the safety gate. Every sentence carries distinct information with no repetition of the title.

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

Completeness4/5

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

For a three-parameter destructive tool with full schema coverage and no output schema, the description covers the action, the notable side effect, and the confirmation requirement. It omits only edge-case behavior (missing key IDs, permission requirements), which is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with the VPS ID pattern and the confirm flag already documented in the schema, so the baseline is 3. The description reinforces the confirm gate and hints that keyId may refer to the web terminal key, but adds no format or lookup guidance beyond that.

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

Purpose4/5

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

States a specific verb and resource ('Delete an SSH key from a VPS'), and the 'from a VPS' scope lets an agent distinguish it from the sibling webspace_delete_ssh_key. It stops short of naming that sibling explicitly, so differentiation relies on the agent reading the target noun carefully.

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

Usage Guidelines3/5

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

Usage is implied by the verb and the confirm requirement, but the description never says when to pick this over webspace_delete_ssh_key or vps_list_ssh_keys, nor what happens if the key ID is unknown. Prerequisites such as the key existing on the VPS are left unstated.

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.