Tools
PV-relevance breakdown
Every tool carries a pvRelevance classification that agents can filter on. Pass params.pvRelevance to tools/list to scope your enumeration.
| Tier | Tools | What's in it |
|---|---|---|
pv-core | 1748 | Tools whose explicit purpose is drug safety surveillance — signal detection, causality, microgram chains, pharma manufacturer entity surfaces, FDA / EMA / ICH / WHO-UMC / international regulators |
pv-adjacent | 265 | Biomedical / chemical infrastructure that supports PV indirectly — clinicaltrials.gov, PubMed, MeSH, ChEMBL, OpenTargets, anatomy / molecular biology |
non-pv | 1049 | General STEM, dev tooling, agent infrastructure — Wolfram, Cargo, Cloud, devtools, observatory |
Filter examples:
POST /api/mcp
Content-Type: application/json
# Only PV-core tools (signal detection, causality, regulatory)
{ "jsonrpc": "2.0", "id": 1, "method": "tools/list",
"params": { "pvRelevance": "pv-core" } }
# PV-adjacent (biomedical infrastructure)
{ "jsonrpc": "2.0", "id": 2, "method": "tools/list",
"params": { "pvRelevance": "pv-adjacent" } }
# Non-PV (general STEM, dev, agent tooling)
{ "jsonrpc": "2.0", "id": 3, "method": "tools/list",
"params": { "pvRelevance": "non-pv" } }Every tool is callable via POST /api/mcp with method tools/call. The Station MCP server at mcp.nexvigilant.com holds the authoritative implementations.
Categories are listed by tool count. Each category links to a summary that lists every tool in that surface; each tool has its own page with input schema and an example call.
Categories
How to enumerate everything programmatically
POST /api/mcp
Content-Type: application/json
{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }Returns all 3062 tool descriptors with input schemas. See /tools.md for the markdown twin (token-budgeted).