# pv-signal-cooperative

`station__pv-compute__pv-signal-cooperative` · external (needs EXECUTION_BACKEND_URL configured) · domain `pv-compute` · pv-relevance `pv-core`

coincidental. Above ~40%, it's likely mechanistic.

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

- `ic_a` *number* (required) — IC value for signal A
- `ic_b` *number* (required) — IC value for signal B
- `patient_overlap` *number* (required) — Patient overlap fraction (Jaccard index, 0.0–1.0)

## Example call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "station__pv-compute__pv-signal-cooperative",
    "arguments": {
      "ic_a": 0,
      "ic_b": 0,
      "patient_overlap": 0
    }
  }
}
```

## Related

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