Skip to main content
Glama

Add SSH key to VPS

vps_upload_ssh_key

Upload an existing SSH public key to a VPS. Optionally store it as the web terminal key.

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>",
      "publicKey": "<publicKey>"
    },
    "name": "vps_upload_ssh_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
publicKeyYesThe SSH public key (must start with ssh-)
displayNameNoOptional display name for the key
useForWebTerminalNoStore the key ID for web terminal access

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds that the key is uploaded rather than generated plus an optional web-terminal side effect. It omits key behaviors an agent would want: whether duplicates are rejected, whether existing keys are affected, and whether the web-terminal key replaces a previous one.

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?

Two short sentences, zero filler, core action front-loaded with the optional behavior second. Nothing is redundant with 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?

A simple additive operation with fully described parameters and annotations that declare its safety profile needs little more; the description covers the essentials. Minor gaps remain around duplicate handling and whether the key is appended to an existing key set.

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 description coverage is 100%, so id, publicKey, displayName, and useForWebTerminal are already documented. The description restates the web-terminal option but adds no format, constraint, or interaction detail beyond the schema, so the baseline 3 applies.

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?

Uses a specific verb and resource ("Upload an existing SSH public key to a VPS") and the word "existing" implicitly contrasts with vps_generate_ssh_key. It never names that sibling or any other alternative, so the differentiation is left for the agent to infer.

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?

"Existing" key hints that generation belongs to a different tool, and the optional web-terminal flag hints at a secondary use. There is no explicit when-to-use/when-not statement and no named alternative, so guidance is only implied.

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.