Skip to main content
Glama

Add an SSH key

add_ssh_key

Saves a public key on the account so new machines can be reached without a password. Scope: sshkeys.write.

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": {
      "name": "<name>",
      "public_key": "<public_key>"
    },
    "name": "add_ssh_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesLabel to recognise the key by, e.g. laptop.
public_keyYesOpenSSH public key, e.g. ssh-ed25519 AAAA… user@host.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"Label to recognise the key by, e.g. laptop."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-destructive, open-world operation. The description adds real value beyond them by naming the required permission scope ('sshkeys.write'), but says nothing about duplicate key handling, account-wide effect limits, or what happens if the same key is added twice.

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 with zero waste; the purpose is front-loaded and the permission scope follows immediately. Nothing needs trimming.

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?

For a simple two-parameter mutation with full schema coverage and annotations, the definition covers purpose and auth scope adequately. The only minor gap is behavior on duplicate labels or keys, which an agent might reasonably wonder about before calling.

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% and both parameters carry examples ('laptop', 'ssh-ed25519 AAAA… user@host'), so the schema does the heavy lifting. The description adds no format or constraint detail beyond what is already documented.

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?

States a specific verb and resource ('Saves a public key on the account') plus the effect it enables ('new machines can be reached without a password'), which is more than a restatement of the title. It does not explicitly contrast with delete_ssh_key or list_ssh_keys, but the verb makes the distinction self-evident.

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?

Usage is implied by the outcome described (enabling passwordless access to new machines), so an agent can infer when this applies. There is no explicit when-to-use/when-not guidance and no named alternative such as list_ssh_keys for inspecting existing keys.

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.