Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Remove Machine

delete_machine
DestructiveIdempotent

Remove a hosted Meshive machine by exact machine_id. Preview with confirm=false, then confirm=true to start deletion; a grace period may apply if other workspaces remain.

Instructions

Remove a hosted machine from Meshive. This can't be undone. machine is the exact machine_id from the machines tool; its name doesn't work. With nothing of other users on it, removal starts at once. Otherwise a grace period of about 48 hours starts and the workspaces using it are emailed; after it, what is left is removed by force and data on local volumes is lost. Powering the machine off or removing its agent during the grace period blocks new machine registrations for 3 months. Its unfinished maintenance windows are cancelled. With confirm=false (default) it only checks what would happen and removes nothing; call again with the same machine_id and confirm=true after the user agreed. A machine already being removed is refused (delete_in_progress). Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

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": {
      "machine": "<machine>"
    },
    "name": "delete_machine"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
machineYes
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructive/openWorld/idempotent, but the description adds substantial context they cannot carry: the immediate-vs-48-hour-grace-period branch, workspace emailing, forced removal and loss of data on local volumes, a 3-month registration block if the machine is powered off mid-grace-period, and cancellation of maintenance windows. It also documents the operation_id lifecycle and the post-timeout recovery path via operation_status.

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?

Front-loaded with the destructive outcome and the identifier constraint, and nearly every sentence carries operational weight. It is dense and a few clauses run together across line breaks, but there is no filler that could be cut without losing behavior the agent needs.

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 destructive, grace-period-driven deletion tool, the description covers prerequisites, side effects, refusal conditions, idempotency via operation_id, and timeout recovery. An output schema exists, so return values need not be explained, and nothing an agent needs before calling is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry all three parameters, and it does: `machine` must be the exact machine_id and names do not work, `confirm=false` is a non-mutating preview, and `operation_id` is a UUID that must be reused across preview, confirmation and retries or a new operation is created. This is meaning well beyond the bare schema titles.

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?

States a specific verb and resource ("Remove a hosted machine from Meshive") and immediately delimits it against the sibling `machines` tool by clarifying that `machine` is the exact machine_id, not a name. The surrounding delete_* siblings are implicitly differentiated by the explicit 'hosted machine' subject.

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?

Gives an explicit workflow: call with confirm=false (default) to preview, then call again with the same machine_id and confirm=true once the user agrees. It also names the source of the identifier (the machines tool) and the refusal case (delete_in_progress), leaving little to inference.

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