AI3D Studio

Retry a batch’s failed pictures

retry_batch

Queue the batch’s failed pictures (and any stopped for want of credits) again as new runs, or only the item_ids given. Charged as each starts, like a new batch of that many pictures: the balance must cover them and they count against a monthly limit.

Input Schema

Name	Required	Description	Default
`batch_id`	Yes	The batch id start_batch returned.
`item_ids`	No

Output Schema

Name	Required	Description
`items`	Yes
`model`	Yes
`scene`	Yes
`counts`	Yes
`status`	Yes
`batch_id`	Yes
`requeued`	Yes	Pictures queued again.
`created_at`	Yes
`item_count`	Yes
`settled_at`	Yes
`quoted_credits`	Yes	What the batch costs if every picture runs.
`charged_credits`	Yes	What its runs were charged so far.
`per_item_credits`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026
- removedOutput schema / properties / items / items / properties / error_code / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / error_code / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / job_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / job_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / settled_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / settled_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds important side-effect context beyond annotations: retries are charged as they start, the balance must cover them, and they count against a monthly limit. With annotations already covering mutability and idempotency, this is strong transparency, though it does not discuss permission or error 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?

Front-loads the action, then adds the critical billing and quota constraints. Two sentences with no wasted text; both earn their place.

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?

Given an output schema, annotations, and only two parameters, the description is mostly complete: it explains scope, optional filtering, cost, and quota impact. Minor gaps remain around item-level edge cases, but nothing essential to invoking it is missing.

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 coverage is 50%; batch_id is documented in the schema and item_ids is not. The description clarifies that item_ids limits the retry to specific items, which compensates somewhat, but it does not add details such as the 100-item cap or item validity requirements.

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?

States a specific verb and resource: queue the batch’s failed pictures again as new runs, with an optional item_ids filter. It is clear what the tool does, though it does not explicitly name start_batch or contrast itself with creating a fresh batch.

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?

The description gives a clear usage context: retry failed pictures or items stopped for lack of credits. It does not provide explicit exclusions or name alternatives, but the intended situation is evident.

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

All AI3D Studio 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?