# dot-dispatch-manifest

`station__dot-ops__dot-dispatch-manifest` · external (needs EXECUTION_BACKEND_URL configured) · domain `dot-ops` · pv-relevance `non-pv`

Dispatch a transit manifest across domains

> **Note:** This tool routes through an external execution backend. If `EXECUTION_BACKEND_URL` is unset on the server, calls return JSON-RPC error `-32603 "Tool execution backend not configured"`. Tools with `backend: native` execute in-process and are always callable.

## Agent metadata

- `idempotent`: unknown
- `read_only`: unknown
- `expected_latency_ms`: unknown (not yet contract-tested)
- `cost_tokens_estimate`: unknown

## Input schema

- `destination` *string* (required) — Destination domain
- `origin` *string* (required) — Origin domain
- `priority` *integer* (required) — Transit priority (1-10)
- `signal_count` *integer* (required) — Number of signals in batch

## Example call

```json
POST /api/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "station__dot-ops__dot-dispatch-manifest",
    "arguments": {
      "destination": "",
      "origin": "",
      "priority": 0,
      "signal_count": 0
    }
  }
}
```

## Related

- [/tools](/tools) — all 3062 tools
- [/tools/dot-ops__dot-dispatch-manifest](/tools/dot-ops__dot-dispatch-manifest) — HTML page
- [/tools/dot-ops__dot-dispatch-manifest/json](/tools/dot-ops__dot-dispatch-manifest/json) — JSON form (agent-friendly)
- [/api/mcp](/api/mcp) — endpoint
- [/AGENTS.md](/AGENTS.md) — agent guide
