Skip to main content
Glama

List webspace SSH keys

webspace_list_ssh_keys
Read-only

List the SSH public keys in a webspace's ~/.ssh/authorized_keys, including the key the dashboard's web terminal uses. Returns per key keyId (SHA-256 fingerprint, for webspace_delete_ssh_key), type, comment and the full key line. Host, port and username for logging in come from webspace_get_ssh_info. For a VPS use vps_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": "webspace_list_ssh_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds non-obvious behavioral detail beyond that: it reads the authorized_keys file and includes the key used by the dashboard's web terminal, which is a real gotcha an agent should know before reporting or reasoning about keys. It stops short of covering pagination, empty-list behavior, or error cases, so it is not a full 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 tight sentences, front-loaded with what is read and where, followed by return shape and cross-references. Every sentence carries information an agent needs; nothing is boilerplate.

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?

No output schema exists, so the description must carry the return contract, and it does by enumerating keyId, type, comment and the full key line. The main remaining gap is how to obtain the webspace id and what an empty result looks like, but for a one-parameter read tool this is close to complete.

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 (id) with 100% schema description coverage ('The webspace ID'), which sets the baseline at 3. The description adds no format, ID-discovery, or sourcing guidance beyond the schema, so it neither compensates nor detracts.

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?

Names a specific verb and resource (list SSH public keys) plus the exact location read (~/.ssh/authorized_keys in a webspace). It explicitly distinguishes scope from the VPS counterpart by naming vps_list_ssh_keys, so an agent can pick correctly without opening 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?

States when to use it versus the VPS alternative ('For a VPS use vps_list_ssh_keys') and routes the agent to webspace_get_ssh_info for host/port/username, which this tool does not return. It also names webspace_delete_ssh_key as the consumer of the returned keyId, closing the workflow loop.

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.