mcp

Import SSH keypair

import_keypair

Registers an existing SSH public key on your account. Use this to import your own public key so you can SSH into instances. The private key never leaves your machine.

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": "import_keypair"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Name for the keypair (e.g. 'my-laptop'). Must be unique on your account.
`public_key`	Yes	SSH public key to import (the contents of your id_rsa.pub or id_ed25519.pub).

Output Schema

Name	Required	Description	Default
`mode`	No
`next`	No
`error`	No
`result`	No
`status`	No
`details`	No
`machine`	No
`message`	No
`request`	No
`recovery`	No
`duplicate`	No
`plan_tool`	No
`needs_plan`	No
`validation`	No
`needs_keypair`	No
`account_notices`	No
`idempotency_key`	No
`source_mismatch`	No
`available_keypairs`	No
`needs_keypair_name`	No
`invalid_keypair_name`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 5, 2026

addedOutput schema / properties / details
```
Added value: +{}
```

addedOutput schema / properties / error / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "not": {}
+      },
+      {
+        "type": "boolean"
+      }
+    ]
+  },
+  {
+    "anyOf": [
+      {
+        "not": {}
+      },
+      {
+        "type": "boolean"
+      }
+    ]
+  }
+]

removedOutput schema / properties / error / type
```
Removed value: -"boolean"
```
addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / recovery
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / status
```
Added value: +{}
```

addedOutput schema / properties / validation / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "not": {}
+      },
+      {}
+    ]
+  },
+  {
+    "anyOf": [
+      {
+        "not": {}
+      },
+      {}
+    ]
+  }
+]

Changed1 schema field changedOct 31, 2026

addedOutput schema / properties / account_notices

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "dismissible": {
+        "type": "boolean"
+      },
+      "id": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "message",
+      "url",
+      "dismissible"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 12, 2026
- addedOutput schema / properties / source_mismatch
```
Added value: +{
+  "type": "boolean"
+}
```
Changed1 schema field changedOct 11, 2026
- addedOutput schema / properties / machine
```
Added value: +{}
```
Changed1 schema field changedJul 8, 2026
- addedOutput schema / properties / plan_tool
```
Added value: +{
+  "type": "string"
+}
```
Changed7 schema fields changedJun 11, 2026
- addedOutput schema / properties / available_keypairs
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / invalid_keypair_name
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / needs_keypair
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / needs_keypair_name
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / needs_plan
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / validation
```
Added value: +{}
```
Changed1 schema field changedJun 11, 2026
- addedOutput schema / properties / next
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedJun 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "duplicate": {
+      "type": "boolean"
+    },
+    "idempotency_key": {
+      "type": "string"
+    },
+    "mode": {
+      "type": "string"
+    },
+    "request": {},
+    "result": {}
+  },
+  "type": "object"
+}

First observedJun 9, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already declare the tool is a non-read-only, non-destructive, non-idempotent write. The description adds useful behavioral context beyond those annotations, especially the security guarantee that the private key never leaves the user's machine.

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?

The description is three short sentences, front-loaded with the core action, followed by usage and a relevant security note. It contains no unnecessary wording.

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 import tool with rich schema coverage, annotations, and an output schema, the description covers purpose, usage, and key security context. It omits details such as duplicate-name behavior, but the schema already states that names must be unique.

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 the schema already explains both name and public_key in detail. The description does not add parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: registering an existing SSH public key on the account. It clearly distinguishes importing a public key from generating one, though it does not explicitly contrast with sibling tools such as list_keypairs or delete_keypair.

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

Usage Guidelines4/5

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

It gives a clear use case: import your own public key so you can SSH into instances. It does not state when not to use the tool or name alternatives, but the intended context is explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?