Skip to main content
Glama
Sign In
vps-mcp

vps-mcp

Official
by vpsdotorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_ssh_key

Remove an SSH key from your account using its unique identifier.

Instructions

Delete an SSH key from your account.

Args: ssh_key_uuid: The UUID of the SSH key to delete

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": {
      "ssh_key_uuid": "<ssh_key_uuid>"
    },
    "name": "delete_ssh_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
ssh_key_uuidYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, and the description only states the action without disclosing side effects (e.g., irreversibility, impact on existing servers using the key) or required permissions. For a mutation tool, this is insufficient.

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?

The description is very concise with two sentences, front-loading the core action and then detailing the parameter. No unnecessary information.

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

Completeness3/5

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

While the tool is simple, the description lacks context about prerequisites, side effects, or relationship to other tools like list_ssh_keys. An output schema exists but is not described, so the agent may not know what to expect upon success or failure.

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 0%, but the description adds a one-line explanation for the sole parameter ('The UUID of the SSH key to delete'), clarifying its role. However, it does not specify format, source, or validation constraints.

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 verb 'Delete' and the resource 'SSH key from your account', which is specific and distinguishes it from siblings like add_ssh_key and list_ssh_keys.

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 explicit guidance on when to use this tool versus alternatives (e.g., when to delete vs. add or list). No mention of prerequisites or contextual conditions for deletion.

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

Deploy Server

Other Tools