run-e2a-outcome-classifier
ICH E2A Section IV.B: Classifies the outcome of an adverse event into 5 standardized ICH categories: recovered, recovering, not_recovered, fatal, unknown — with follow-up implications
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
death_confirmedbooleanrequired — Input parameter: death_confirmedsymptoms_resolvedbooleanrequired — Input parameter: symptoms_resolvedae_ongoingbooleanrequired — Input parameter: ae_ongoingrecovered_with_sequelaebooleanrequired — Input parameter: recovered_with_sequelaesigns_improvingbooleanrequired — Input parameter: signs_improvingoutcome_knownbooleanrequired — Input parameter: outcome_known
Example call
POST /api/mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "station__microgram__run-e2a-outcome-classifier",
"arguments": {
"death_confirmed": false,
"symptoms_resolved": false,
"ae_ongoing": false,
"recovered_with_sequelae": false,
"signs_improving": false,
"outcome_known": 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-e2a-outcome-classifier/raw.md — this page's Markdown twin