routing.preview
V1.1 · post-MVPDry-run a decision and return the would-be-dispatched handler. (Preview — V1.x+.)
Description
Stub-ships at MVP returning feature_not_available with adr/section/shipping pointers. Depends on the V1.x+ cross-app routing engine. Per ADR-0021 §routing-preview.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
action_class | string | yes | The action class to preview. |
counterparty_id | string | no | Optional counterparty. |
mode | 'ask' | 'notify' | 'silent' | no | Optional mode. |
Output shape
typescript
{ ok: false; error: "feature_not_available"; details: { adr: "ADR-0021"; section: "§routing-preview"; shipping: "V1.x+" } }Example call
JSON-RPC tools/call request body (omit the JSON-RPC envelope when using an SDK; the SDK adds it for you):
jsontools/call params
{ "name": "routing.preview", "arguments": { "action_class": "communicate", "counterparty_id": "entity_01HXSARAH" } }Example response
Tool results are always wrapped as content[0].text with a stringified JSON body. The shape below is what you get back from JSON.parse(result.content[0].text):
jsonparsed result body
{ "ok": false, "error": "feature_not_available", "details": { "adr": "ADR-0021", "section": "§routing-preview", "shipping": "V1.x+" } }Errors this tool can return
| Code | Meaning |
|---|---|
invalid_arguments | Tool input failed Zod validation. |
unauthorized | Missing or invalid bearer token. |
feature_not_available | The tool is registered but the underlying capability is not wired in this build. |
See the full error catalog for resolution steps on each code, plus the standard transport-layer responses (401, 429).