Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Retry Machine Setup

retry_machine_setup
Idempotent

Retry a hosted machine's failed setup step or recheck its ports without confirmation, like the console's Retry buttons.

Instructions

Retry a hosted machine's failed setup step (check="setup") or check its ports again (check="ports"), like the console's Retry buttons; neither asks for confirmation. machine is the machine_id from the machines tool. Retrying a step the machine's agent runs reboots the machine first, and only a failed step can be retried (not_retryable). Port checks have a cooldown of about 30 seconds between them (port_check_cooldown). Both run in the background: poll the machines tool for the machine's state, and its boot_report for the port results. A port check keeps no operation record: operation_status can't look it up, and calling again checks again (or hits the cooldown). 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": "retry_machine_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkNosetup
machineYes
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which only say not read-only, open-world, idempotent, non-destructive), the description discloses that neither mode prompts for confirmation, that retrying an agent-run step reboots the machine first, that both modes run asynchronously and must be polled, and that port checks leave no operation record. These are exactly the side effects an agent needs before firing the call.

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?

The purpose is front-loaded and the mode-specific constraints follow logically. The trailing operation_id paragraph reads as cross-tool boilerplate, and the source text carries awkward mid-sentence line breaks, but nothing is genuinely redundant.

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 three-parameter mutation tool with an output schema, the definition covers the async lifecycle, where to poll for results (machines state and boot_report), retry preconditions, cooldown behavior, and the operation_id contract. Nothing an agent needs in order to call it correctly 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 description coverage is 0%, so the description must carry all parameter meaning — and it does: `machine` is the machine_id from the machines tool, `check` is implicitly setup-or-ports with distinct semantics, and `operation_id` must be reused from the preview or generated as a UUID, with a new ID meaning a new operation. This is the only source of these constraints.

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 first clause names a specific verb (retry) and resource (a hosted machine's failed setup step) and immediately disambiguates the two modes via check="setup" vs check="ports". An agent can distinguish this from sibling tools like machines or operation_status without opening the schema.

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 real preconditions and exclusions: only a failed step is retryable (not_retryable), port checks share a ~30s cooldown (port_check_cooldown), and operation_status cannot look up a port check. It also routes polling to the machines tool and boot_report. What it lacks is an explicit statement of when to prefer a different remediation path (e.g. reinstall or delete_machine) instead of retrying.

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