AgentsPodium Hosting

Rebuild instance

rebuild_instance

Destructive

Rebuild an instance's pod (e.g. after a config change that needs a restart).

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.8/5.0

Behavior3/5

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

The annotations already declare destructiveHint=true and openWorldHint=true, so the description does not need to restate that this is destructive. The description adds the restart-after-config-change context, which is useful, but it does not detail what exactly gets destroyed or whether the instance becomes unavailable during the rebuild.

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?

One concise sentence with the core action first and the use case in parentheses. Every word earns its place with no redundant filler.

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 single-parameter tool with annotations covering destructiveness and side effects, the description is nearly sufficient. The only missing piece is a brief note about the operational impact on the running instance, but this is minor given the simple interface.

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?

Schema description coverage is 100%, and the single parameter 'id' already has a clear description referencing create_instance and list_instances. The tool description adds no additional parameter-level information, so the baseline of 3 applies.

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 clearly states a specific action—'Rebuild an instance's pod'—and gives a concrete motivating example. It is distinguishable from siblings like pause_instance or delete_instance, though 'rebuild' is not deeply elaborated.

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 a clear use case: 'after a config change that needs a restart.' This provides practical context for when to invoke the tool, though it does not explicitly discuss when not to use it or name alternatives.

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.