Skip to main content
Glama

hostodo_remove_ssh_key

Remove an SSH key from a Hostodo VPS. Provide the instance or resource ID to specify which key to delete.

Instructions

Coming soon (access): Remove an SSH key. This PMF stub records demand and returns a structured coming_soon response; it does not perform the requested action yet. Do not send secrets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vm_idNoOptional Hostodo instance id, hostname, or unique prefix when relevant.
intentNoOptional brief description of what the user wanted to do.
metadataNoOptional non-secret request metadata for PMF discovery.
resource_idNoOptional invoice/ticket/zone/deployment/resource id when relevant.
Behavior5/5

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

Fully transparent: it admits it's a stub, records demand, returns a coming_soon response, and performs no action. Also warns against sending secrets.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences, but the first sentence 'Coming soon (access): Remove an SSH key.' is slightly awkward in structure. No waste.

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 stub tool, the description fully explains what it does and its limitations. No output schema needed; the behavior as a placeholder is adequately described.

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 coverage is 100% but description adds no meaning beyond the schema. Parameters are optional and loosely described; the description does not reference them.

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 clearly states 'Remove an SSH key' but immediately clarifies it's a stub that does not perform the action, making its purpose as a demand-recording placeholder unmistakable.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like hostodo_add_ssh_key or hostodo_list_ssh_keys. It only warns not to send secrets, implying it's not for actual removal.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hostodo/hostodo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server