# Microgram: data-sufficiency-gate

`station__algovigilance__microgram-data-sufficiency-gate` · native (always callable) · domain `algovigilance` · pv-relevance `pv-core`

Assesses whether sufficient data exists to proceed to the next analysis step in a PV investigation

## Agent metadata

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

## Input schema

- `drug_identified` *boolean* — Whether the suspect drug has been identified
- `event_identified` *boolean* — Whether the adverse event has been clearly identified
- `has_temporal_relationship` *boolean* — Whether temporal relationship between drug and event is established
- `has_dechallenge` *boolean* — Whether dechallenge information is available
- `report_count` *number* — Number of reports supporting the signal

## Example call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "station__algovigilance__microgram-data-sufficiency-gate",
    "arguments": {}
  }
}
```

## Related

- [/tools](/tools) — all 7718 tools
- [/tools/algovigilance__microgram-data-sufficiency-gate](/tools/algovigilance__microgram-data-sufficiency-gate) — HTML page
- [/tools/algovigilance__microgram-data-sufficiency-gate/json](/tools/algovigilance__microgram-data-sufficiency-gate/json) — JSON form (agent-friendly)
- [/api/mcp](/api/mcp) — endpoint
- [/AGENTS.md](/AGENTS.md) — agent guide