# pv-taxonomy-concept

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

Look up a T3 concept by pillar and name.

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

- `name` *string* (required) — Concept name within the pillar (e.g., "prr", "naranjo_algorithm", "rems").
- `pillar` *string* (required) — Pillar: "detection", "assessment", "understanding", "prevention", "regulatory", "infrastructure", "operations", "analytics", "safety_comms", "special_populations", "scope".

## Example call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "station__pv-compute__pv-taxonomy-concept",
    "arguments": {
      "name": "",
      "pillar": ""
    }
  }
}
```

## Related

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