Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Edit Pod

update_pod
Idempotent

Modify an existing Meshive pod by passing only changed hardware, ports, storage, environment, command, or template settings, with a preview and confirmation before applying.

Instructions

Change an existing pod like the console's Edit: pass only what changes. pod is the pod_name from the pods tool (its display name works on the preview; confirm with the returned pod_name). With confirm=false (default) it only returns the server's estimate (the changes, the hourly price before and after, and whether the pod restarts) and changes nothing; call again with confirm=true after the user agreed. A running pod restarts with the new settings and a stopped pod uses them at its next start; renaming alone (name) doesn't restart it. Input assets and watched folders are kept. Locked like the console: the pod type (GPU or CPU), premiums and the image can't change. Hardware: gpu_model/gpu_vram_gb/gpu_count for GPU pods, cpu_line for CPU pods, rental_type demand or spot. Changing the GPU resets vCPU and RAM per GPU to the new GPU's recommended sizes, changing only gpu_count keeps the per-GPU ratio, and changing the CPU line resets cores and RAM to the console's default. vcpu and ram_gb are pod totals and must be sizes the console offers. An older pod may need ram_gb passed with any change. template_id moves the pod to another template; its variables, ports and command then start from that template, and the preview's changes list what was added before that doesn't carry over. env sets or adds variables (secret_keys names the secret ones) and remove_env removes variables the user added. ports opens new ports, template_ports renames, renumbers or exposes/hides current ports ([{"port": 8188, "name": "ui", "new_port": 8189, "external": false}]) and remove_ports closes ports the user added. Template variables and ports can't be removed. command replaces the start command ("" = back to the template's). Port locks: a port this edit newly exposes over HTTPS (an external port in ports, a port set to "external": true) is locked, so only signed-in workspace members and requests with the port's access key get through; a new template's ports follow that template (open_by_template in the preview). lock_public_ports=false, or "locked": false on its item, leaves it open to anyone who knows the URL: only when the user explicitly asks. A port that is exposed already keeps its lock; set_port_lock changes it without a restart. The preview lists locked_ports and open_ports. Storage: volumes attaches existing network storage ([{"storage": pv_name, "mount_path": "/data"}]) or local storage on the pod's current machine; local_volumes creates new local storage like create_pod (at least 10 GiB, billed hourly until deleted); detach_storages lists pv_names to detach (the storage and its data stay). Names work on previews; confirm with the returned ids. Spot pods can't have local storage, so detach it to switch to spot. If the pod's machine can't fit the change, the call fails with node_migration_required and nothing changes. Only after the user agrees to a move, call again with allow_node_migration=true. A move permanently deletes any scratch disk the pod has; then allow_data_loss=true is also needed, only after separate explicit consent (it is only sent together with allow_node_migration). If the edit would leave watched folders on no attached storage, it fails with harvest_roots_orphaned and their paths; after the user agrees to remove them, pass them as drop_watched_folders. enable_folder_saving=true adds the uploader to an older pod that has none (watched_folders shows editable false with reason no_sidecar), so its folders can be watched; it needs storage on the pod and restarts a running pod once. max_price_per_hour refuses the edit when the new estimate is above it. 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": {
      "pod": "<pod>"
    },
    "name": "update_pod"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
podYes
nameNo
vcpuNo
portsNo
ram_gbNo
commandNo
confirmNo
volumesNo
cpu_lineNo
gpu_countNo
gpu_modelNo
workspaceNo
remove_envNo
gpu_vram_gbNo
rental_typeNo
secret_keysNo
template_idNo
operation_idNo
remove_portsNo
local_volumesNo
template_portsNo
allow_data_lossNo
detach_storagesNo
lock_public_portsNoLeave it true (the default): a port this edit newly exposes over HTTPS is locked (a new template's ports follow that template's own setting, and the preview lists the ones it leaves open as `open_by_template`). false leaves the newly exposed ports open to anyone who knows the URL: pass it only when the user explicitly asked for that. A port that is exposed already keeps its lock either way.
max_price_per_hourNo
allow_node_migrationNo
drop_watched_foldersNo
enable_folder_savingNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.0
    • addedInput schema / properties / lock_public_ports
      Added value: +{
      +  "default": true,
      +  "description": "Leave it true (the default): a port this edit newly exposes over HTTPS is locked (a new template's ports follow that template's own setting, and the preview lists the ones it leaves open as `open_by_template`). false leaves the newly exposed ports open to anyone who knows the URL: pass it only when the user explicitly asked for that. A port that is exposed already keeps its lock either way.",
      +  "title": "Lock Public Ports",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes far beyond the annotations: running pods restart while stopped pods apply at next start, renaming alone doesn't restart, input assets and watched folders persist, GPU/CPU/premium/image fields are locked, GPU changes reset vCPU/RAM ratios, and template_id resets variables/ports/command with a preview listing what doesn't carry over. It also discloses the node_migration_required and harvest_roots_orphaned failure modes with their remediation flags, the scratch-disk deletion risk, port-lock defaults, and the operation_id retry contract.

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?

Very long, but organized into topical paragraphs (hardware, template, env/ports, port locks, storage, migration, watched folders, operation_id) and front-loaded with the confirm workflow. Density is justified by the 29-parameter surface, though a few clauses (e.g. the repeated port-lock restatement) could be trimmed for faster scanning.

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?

Complete for a 29-parameter mutation tool: every user-visible consequence, error path, restart side effect, and irreversible action is spelled out, and the preview fields (changes, prices, restarts, locked_ports/open_ports) are described even though an output schema also exists. An agent could drive this tool end-to-end, including consent gates and retry handling, from the description alone.

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 only 3% across 29 parameters, but the prose supplies concrete meaning for essentially all of them, including example payloads for volumes and template_ports, the empty-string reset for command, the totals-vs-per-GPU distinction between vcpu/ram_gb and gpu_count, and the pairing constraint that allow_data_loss is only sent with allow_node_migration.

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 ("Change an existing pod") and immediately pins the update semantics with "like the console's Edit: pass only what changes." It also frames the two-phase preview/confirm behavior up front, which distinguishes it from create_pod and from direct mutators like restart_pod.

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?

Explicit when-to-use rules throughout: confirm=false returns only an estimate and confirm=true comes after user agreement; allow_node_migration only after agreeing to a move; allow_data_loss only after separate explicit consent and only alongside migration; lock_public_ports=false and "locked": false only when the user explicitly asks; set_port_lock is named as the no-restart alternative for changing an existing port's lock.

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