Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Set Machine Listing

set_machine_listing
Idempotent

Lists or unlists a hosted machine to control new pod placement: listed=true allows scheduling, while listed=false blocks it and requires confirmation.

Instructions

List a hosted machine (listed=true) so new pods can be placed on it, or unlist it (listed=false), like the console's listing switch. machine is the machine_id from the machines tool. Listing needs no confirmation. It is checked first: a machine that can't be listed yet is refused with the console's reason (listing_refused), and nothing changes. Unlisting stops new pods from being placed on the machine, and stopped pods can't start on it again until it is listed; running pods keep running. With listed=false and confirm=false (default) it only says how many pods run on it and changes nothing; call again with confirm=true after the user agreed. 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>",
      "listed": "<listed>"
    },
    "name": "set_machine_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
listedYes
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 declare the safety profile (destructiveHint=false, idempotentHint=true), and the description adds substantial context beyond them: unlisting blocks new pod placement and blocks stopped pods from restarting while running pods keep running, listing eligibility is checked first and refused with a listing_refused reason leaving state unchanged, and operation_id must be reused across confirmation and retries.

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 scope and the list/unlist semantics are front-loaded, and every sentence carries operational information. It is slightly dense and the embedded line breaks make it harder to scan, but nothing is truly 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?

An output schema exists, so return values need not be described. For a 4-parameter mutation tool with a preview-then-confirm flow, the description supplies the preconditions, side effects, refusal behavior, and idempotency contract an agent needs to call it correctly.

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 carries the full burden and does: machine is the machine_id from the machines tool, listed is the switch itself, confirm governs whether unlisting is a no-op preview, and operation_id must be reused for the same operation or a new one is created. All four parameters gain meaning beyond their types.

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 pair and resource: list (listed=true) or unlist (listed=false) a hosted machine so pods can be placed on it. It also names the sibling tool that supplies the identifier ('`machine` is the machine_id from the machines tool'), so an agent can distinguish it from machines and set_port_lock without opening another schema.

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?

Explicitly covers when-to-use and how: listing needs no confirmation, unlisting with confirm=false is a preview-only call, and the agent must re-call with confirm=true after the user agrees. It also gives retry guidance ('after a timeout, check operation_status and resource state before retrying'), naming the relevant sibling.

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