run-epa5-signal-detect
EPA 5: Detect and validate safety signals — routes by signal strength, evidence quality, and clinical significance.
Taxonomy
Linnaean classification joined from the algovigilance taxonomy index via the parent config's rank.
| Rank | Value |
|---|---|
| domain | Substrata |
| kingdom | Constructa |
| phylum | Configa |
| class | station-config |
| order | microgram |
| family | mcp-tool-config |
Characteristics:
- substrate:
config - domain:
pv - lifecycle:
continuous - authority:
read - compounding:
producer - io:
agent-request→tool-response
Input schema
prrnumberrequired — Input parameter: prrclinical_significancestringrequired — Input parameter: clinical_significancecase_countintegerrequired — Input parameter: case_counthas_biological_plausibilitybooleanrequired — Input parameter: has_biological_plausibilitychi_squarednumberrequired — Input parameter: chi_squaredhas_literature_supportbooleanrequired — Input parameter: has_literature_support
Example call
POST /api/mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "station__microgram__run-epa5-signal-detect",
"arguments": {
"prr": 0,
"clinical_significance": "",
"case_count": 0,
"has_biological_plausibility": false,
"chi_squared": 0,
"has_literature_support": false
}
}
}How to invoke from a client
From any MCP-aware client, add https://algovigilance.com/api/mcp as an MCP server, then call this tool by name. From a raw HTTP client, send the JSON-RPC body above to /api/mcp.
Agent-friendly formats
Working inside an AI assistant? Use the Copy for AI button at the top of this page (or view the raw Markdown) to paste a clean, token-budgeted version of this tool's contract into your conversation.
Related
- All tools (3062 live)
- /api/mcp — endpoint
- /AGENTS.md — agent guide
- /tools/microgram__run-epa5-signal-detect/raw.md — this page's Markdown twin