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.

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
`mode`	No
`next`	No
`error`	No
`result`	No
`request`	No
`duplicate`	No
`plan_tool`	No
`needs_plan`	No
`validation`	No
`needs_keypair`	No
`idempotency_key`	No
`available_keypairs`	No
`needs_keypair_name`	No
`invalid_keypair_name`	No

TDQS

A4.2/5.0

Behavior4/5

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

The description adds value beyond annotations by stating 'The private key never leaves your machine', a key security trait. While annotations provide destructiveHint=false and readOnlyHint=false, the description clarifies the operation's safety regarding private key exposure. It does not contradict annotations.

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 sentences with zero waste: first states purpose, second suggests usage, third discloses key behavioral detail. Optimal length for a simple tool.

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?

Given the tool's simplicity (2 parameters, output schema exists), the description covers purpose, usage, and a critical behavioral trait. It does not mention error conditions like duplicate names or invalid key format, but the schema handles uniqueness constraint. Adequately complete for the complexity level.

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 covers 100% of parameters with descriptions. The tool description adds no new semantic detail about parameters beyond the schema's 'Name for the keypair' and 'SSH public key to import'. Baseline 3 is appropriate.

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 uses specific verb 'registers' and resource 'existing SSH public key', clearly stating the tool's action. It distinguishes from siblings like 'delete_keypair' and 'list_keypairs' by specifying importing an existing key rather than generating or deleting.

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?

The description explicitly says 'Use this to import your own public key so you can SSH into instances', providing clear when-to-use guidance. It does not mention when not to use or alternatives, but no alternative key generation tool exists among siblings, so this is acceptable.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose, and the descriptions include specific details (e.g., create_database for Postgres vs create_relational_database for MySQL/MariaDB) that prevent confusion. Even similar tools like plan_deploy, plan_instance, and plan_managed_datastore are well-differentiated by their contexts.

Naming Consistency5/5

The vast majority of tools follow the verb_noun pattern with underscores (create_*, list_*, delete_*, etc.). Only minor deviations like 'whoami' exist, but the overall pattern is highly consistent and predictable.

Tool Count2/5

With 69 tools, the server has an excessive number for an MCP context, far exceeding the typical 3-15 range. While it may mirror the full redu.cloud API, the sheer count overwhelms agents and increases selection latency.

Completeness4/5

The tool set covers the majority of cloud management operations: CRUD for instances, volumes, databases, deployments, and more. However, update operations are missing for several resources (e.g., instance resize, volume resize), and there is no tool to modify deployments without redeploying.

Resources

Need Help?