# pipeline-transfer

`station__pipeline__pipeline-transfer` · external (needs EXECUTION_BACKEND_URL configured) · domain `pipeline` · pv-relevance `non-pv`

Look up cross-domain transfer mappings for signal-pipeline types.

> **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

- `domain` *string* — Target domain to filter by (e.g. "Biology", "Cloud")
- `source_type` *string* — Source type name to look up transfers for (e.g. "ContingencyTable", "DetectionResult")

## Example call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "station__pipeline__pipeline-transfer",
    "arguments": {}
  }
}
```

## Related

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