Skip to main content
Glama

List VPS SSH keys

vps_list_ssh_keys
Read-only

List the SSH keys Sitequest manages for logging in to a VPS, as added with vps_upload_ssh_key or vps_generate_ssh_key. Keys written into authorized_keys by hand are not included. Returns keyId, displayName, createDate, publicKey and isWebTerminalKey (the key the dashboard's web terminal uses). Remove a key with vps_delete_ssh_key and its keyId. For webspaces use webspace_list_ssh_keys.

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_list_ssh_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a non-mutating read. Beyond that, the description discloses data provenance (only keys added through the Sitequest tooling appear) and enumerates the returned fields, including the meaning of isWebTerminalKey. It stops short of mentioning behavior on an empty result set or any pagination/auth requirements, which keeps 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?

Four short sentences, each doing distinct work: what is listed, what is excluded, what is returned, and where to go for related operations. The scope statement is front-loaded ahead of alternatives, with no filler or restated title.

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 single-parameter read tool with no output schema, the definition covers purpose, exclusions, return fields, and navigation to the add/delete/webspace counterparts. An agent has everything needed to select and call it correctly; only an empty-result note would be a marginal addition.

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?

There is a single required parameter and schema description coverage is 100%, so the schema already states that 'id' is the VPS ID with a 24-hex-char pattern. The description implies the identifier relates to the VPS being queried but adds no format or scope detail beyond the schema, matching the baseline for full coverage.

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 names a specific verb and resource ('List the SSH keys Sitequest manages') and immediately narrows scope with the exclusion 'Keys written into authorized_keys by hand are not included.' It also contrasts itself with the sibling webspace_list_ssh_keys, so an agent can distinguish it without reading either 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 routes the agent explicitly: creation is done via vps_upload_ssh_key or vps_generate_ssh_key, removal via vps_delete_ssh_key using the returned keyId, and webspaces go to webspace_list_ssh_keys. Both the when-to-use and the when-not-to-use cases are stated rather than 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.