run-escalation-decision
Determines whether a safety finding should be escalated to a human pharmacovigilance officer
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
involves_pediatricbooleanrequired — Input parameter: involves_pediatricis_unexpectedbooleanrequired — Input parameter: is_unexpectedis_fatalbooleanrequired — Input parameter: is_fatalsignal_strengthstringrequired — Input parameter: signal_strengthinvolves_pregnancybooleanrequired — Input parameter: involves_pregnancy
Example call
POST /api/mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "station__microgram__run-escalation-decision",
"arguments": {
"involves_pediatric": false,
"is_unexpected": false,
"is_fatal": false,
"signal_strength": "",
"involves_pregnancy": 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-escalation-decision/raw.md — this page's Markdown twin