run-e2a-ae-vs-adr
ICH E2A Section 2: Classify whether an event is an Adverse Event (AE) or Adverse Drug Reaction (ADR) based on causal relationship and temporal association
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
temporal_associationbooleanrequired — Input parameter: temporal_associationreasonable_causal_relationshipstringrequired — Input parameter: reasonable_causal_relationshipoccurred_during_studybooleanrequired — Input parameter: occurred_during_study
Example call
POST /api/mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "station__microgram__run-e2a-ae-vs-adr",
"arguments": {
"temporal_association": false,
"reasonable_causal_relationship": "",
"occurred_during_study": 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-ae-vs-adr/raw.md — this page's Markdown twin