rhino_batch_call
Dispatch multiple Rhino bridge methods in a single round-trip to reduce latency for workflows with consecutive automation calls.
Instructions
Dispatch multiple bridge methods in a single round-trip.
IMPORTANT: ``steps[].method`` is a **bridge dispatcher route**, not
an MCP tool name. The MCP tool ``rhino_layer_create`` maps to the
dispatcher route ``rhino.layer.create``; ``rhino_document_summary``
maps to ``rhino.query.document_summary`` (NOT ``rhino.document.summary``).
Standalone-only tools (``rhino_set_user_text`` etc. that have no
``bridge_call`` path) cannot be batched. A wrong route name returns
an ``error`` row with ``HandlerError``; the batch aborts when
``on_error='stop'``.
Measured impact (v0.6.x, localhost): direct sequential layer.create
~580ms/op vs batched ~340ms/op — N x ~240ms saved per batch (the
MCP↔bridge round-trip cost paid once instead of N times). Effective
for any workflow that issues >5 bridge calls back-to-back.
Returns ``{summary: {total, ok, failed, on_error}, results: [...]}``
where each ``results`` entry has ``index``, ``method``, ``status``
(``"ok"`` | ``"error"``), and either ``result`` or ``error``.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| args | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||