Cloud World Model

Recover Failed Resource

simulation.recover_resource

Recover one reversible failed resource in a temporary anonymous demo simulation. No API key required for this temporary anonymous demo operation. Lower traffic to a serviceable level first, then provide resourceId or resourceName from simulation.create, simulation.step, or simulation.metrics. This deactivates applicable instance_down/database_overload failures for only the selected resource and returns recoveryProgress with parked, cooling_down, or healthy state plus cooldown counters. It cannot restore an instance_kill because that failure permanently removes the resource. The likely next tool is simulation.step; keep stepping and inspect the targeted resource until recoveryProgress.state is healthy. Pass simulationId from simulation.create when using a fresh MCP session; a preserved session may omit it. Authenticate with an API key to unlock all 63 tools and unlimited simulations.

Input Schema

TableJSON Schema

Name	Required	Description
`resourceId`	No	ID of the failed resource to recover
`resourceName`	No	Exact case-insensitive name of the failed resource to recover
`simulationId`	No	Simulation ID returned by simulation.create. Preserve Mcp-Session-Id to omit this field and use the session's current simulation; if your connector starts a fresh MCP session for each call (for example Grok Bot or Cursor), pass this explicit ID after every fresh initialization. A fresh session has no current-simulation pointer and returns NO_ACTIVE_SIMULATION when the ID is omitted. Anonymous capabilities are short-lived (30 minutes by default), unguessable, and revoked when the demo expires or is deleted; proxy IP changes do not invalidate them. Do not treat the ID as a durable share link.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`simulationId`	No
`recoveryState`	No
`previousHealth`	No
`stepsToHealthy`	No
`recoveryProgress`	No
`resolvedResourceId`	No
`simulationIdSource`	No
`resolvedResourceName`	No
`deactivatedFailureIds`	No
`stepsToHealthyIsLowerBound`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / properties / recoveryProgress / properties / state / enum

Previous value: -[
-  "parked",
-  "cooling_down",
-  "healthy"
-]New value: +[
+  "parked",
+  "blocked",
+  "cooling_down",
+  "healthy"
+]

AddedAug 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say non-read-only, non-destructive, non-idempotent; the description goes well beyond by disclosing that only the selected resource's instance_down/database_overload failures are deactivated, that recoveryProgress returns parked/cooling_down/healthy plus cooldown counters, and that instance_kill failures are unrecoverable.

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 core action and its constraints, and most sentences earn their place. Some repetition around the anonymous-demo/no-API-key framing and the closing upsell sentence slightly dilute density.

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 recovery mutation with an output schema, the description covers preconditions, scope of effect, unrecoverable cases, return-state semantics, and session handling. An agent has everything needed to call it and interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds genuine value on top: it tells the agent where each identifier originates (simulation.create/step/metrics) and gives session guidance for simulationId, though it doesn't clarify precedence between resourceId and resourceName.

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 (recover) plus resource (one reversible failed resource) and scopes it to a temporary anonymous demo simulation. It also distinguishes itself from siblings by naming simulation.create/step/metrics as ID sources and simulation.step as the follow-up tool.

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 preconditions (lower traffic to a serviceable level first), explicit inputs to source (resourceId or resourceName from create/step/metrics), explicit exclusion (cannot restore an instance_kill), and an explicit next step (simulation.step until healthy). Nothing is left to inference.

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

All Cloud World Model tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?