AgentsPodium Hosting

Resume instance

resume_instance

Idempotent

Resume a previously paused instance, rebuilding it from its archive.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Instance (agent) id, as returned by create_instance or list_instances.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Instance (agent) id.
`name`	Yes	Display name.
`tier`	Yes	Hosting plan id.
`a2aUrl`	Yes	A2A JSON-RPC endpoint for the instance, or null if A2A is not enabled.
`domain`	Yes	Customer-owned domain serving the instance, or null.
`engine`	Yes	Runtime engine id (e.g. hermes).
`status`	Yes	Lifecycle status (e.g. running, stopped).
`createdAt`	Yes	ISO timestamp when the instance was created.
`endpointUrl`	Yes	Public HTTPS endpoint for the instance, or null if not yet assigned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "a2aUrl": {
+      "description": "A2A JSON-RPC endpoint for the instance, or null if A2A is not enabled.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "createdAt": {
+      "description": "ISO timestamp when the instance was created.",
+      "type": "string"
+    },
+    "domain": {
+      "description": "Customer-owned domain serving the instance, or null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "endpointUrl": {
+      "description": "Public HTTPS endpoint for the instance, or null if not yet assigned.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "engine": {
+      "description": "Runtime engine id (e.g. hermes).",
+      "type": "string"
+    },
+    "id": {
+      "description": "Instance (agent) id.",
+      "type": "string"
+    },
+    "name": {
+      "description": "Display name.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Lifecycle status (e.g. running, stopped).",
+      "type": "string"
+    },
+    "tier": {
+      "description": "Hosting plan id.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "engine",
+    "tier",
+    "status",
+    "endpointUrl",
+    "a2aUrl",
+    "domain",
+    "createdAt"
+  ],
+  "type": "object"
+}

First observedSep 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The description adds useful behavioral context by saying the instance is 'rebuilt from its archive', going beyond the annotations. However, it does not disclose what happens to the current instance state, whether data is replaced, or any side effects despite openWorldHint suggesting possible unspecified behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence that places the main action first and adds a meaningful qualifier ('previously paused', 'from its archive'). No words are wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with an output schema, the description covers the essential trigger condition and the rebuilding behavior. It is adequate, though it could be more complete by clarifying post-resume state or explicit differences from rebuild_instance.

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

Parameters3/5

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

The input schema already provides complete coverage of the single 'id' parameter, including where the id comes from. The description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-resource pair ('Resume ... instance') and adds the condition 'previously paused', which makes the core purpose clear. It does not explicitly differentiate itself from the sibling rebuild_instance, though the paused-state condition provides some distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for paused instances only, but it does not explicitly state when not to use it or how it differs from rebuild_instance. There are no exclusions or alternative-selection cues.

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

All AgentsPodium Hosting 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.