batch
[batch]
Run ordered tool operations in one request.
Unreleased read-only preview. Technical reference for agents and client integrators.
Before this call
Nested batches and send_feedback are forbidden. Lifecycle operations can change generations and execute trusted imports; this is not an atomic transaction.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| operations | json | Yes | Array of 1 to 50 objects. Each requires tool (string); arguments is an optional object. |
Examples
Technical examples for agents and client integrators. Replace paths and opaque keys with returned workspace values.
Illustrative arguments
Arguments
{
"operations": [
{
"tool": "server_status"
},
{
"tool": "get_structure",
"arguments": {
"path": "src/main/java/example/OrderService.java"
}
}
]
}Full MCP request
Full MCP request
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "batch",
"arguments": {
"operations": [
{
"tool": "server_status"
},
{
"tool": "get_structure",
"arguments": {
"path": "src/main/java/example/OrderService.java"
}
}
]
}
}
}Response notes
Results follow operation order. Each inner result reports its observed generation. A 128 KiB overflow omits results and reports attempted counts. All operations retain their effects.