Skip to main content
Glama

Generate VPS SSH key

vps_generate_ssh_key

Have Sitequest generate a new SSH key pair for a VPS and add its public key to the VPS's managed keys. The private key is never returned: with useForWebTerminal it is stored encrypted for the dashboard's web terminal, otherwise it is discarded. So this is for the web terminal only; to let a person or a CI system log in, ask for their public key and use vps_upload_ssh_key. Returns keyId, displayName, publicKey and webTerminalKeyId.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
displayNameNoName shown in vps_list_ssh_keys, e.g. 'web terminal'
useForWebTerminalNoStore the private key encrypted for the dashboard's web terminal. Without it the private key is discarded

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the critical trait that the private key is never returned, that it is stored encrypted only when useForWebTerminal is set, and otherwise discarded irrecoverably. It also enumerates the returned fields, which is valuable given no output schema exists.

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?

Four short sentences, front-loaded with the action, then the privacy consequence, then the routing rule, then the return fields. No filler and no repetition that does not serve a decision.

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

Completeness5/5

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

For a three-parameter mutation with no output schema, the description covers the action, the irreversible side effect, the alternative tool, and the response shape. Nothing an agent needs in order to call this correctly or avoid calling it wrongly is missing.

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% and the schema already documents that useForWebTerminal stores the key encrypted versus discarding it, so most of the description's parameter content is restatement. It adds a modest framing benefit by tying the flag to the web-terminal-only use case, but gives no extra detail on id or displayName beyond the schema.

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 opening sentence names a specific verb and resource — generate a new SSH key pair, add the public key to the VPS's managed keys — and the closing guidance explicitly contrasts it with vps_upload_ssh_key. An agent can distinguish it from the sibling set without opening the schema.

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

Usage Guidelines5/5

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

It states a hard exclusion ("this is for the web terminal only") and names the exact alternative for the other case ("ask for their public key and use vps_upload_ssh_key"), including the human/CI scenario that selects it. Both when-to-use and when-not-to-use are explicit.

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.