Microgram: site-dev-strategy-router
NexVigilant site development strategy router. Checks 4 prerequisite gates in dependency order (Academy→Glass bridge, Microgram→Station wiring, Worked example, External traffic) and routes to the first unmet gate. Source: 20Q Scramble game session 2026-03-22.
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 | algovigilance |
| family | mcp-tool-config |
Characteristics:
- substrate:
config - domain:
pv - lifecycle:
continuous - authority:
read - compounding:
producer - io:
agent-request→tool-response
Input schema
academy_glass_readyboolean — Academy-to-Glass bridge operational: L1→L2→L3 pathway connects learners to Station toolsmicrogram_station_wiredboolean — Micrograms exposed through Station MCP tools: decision trees callable by any agentworked_example_publishedboolean — Semaglutide worked example published: complete reproducible signal investigationexternal_traffic_measuredboolean — External agent traffic measured and nonzero at mcp.nexvigilant.com
Example call
POST /api/mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "station__algovigilance__microgram-site-dev-strategy-router",
"arguments": {}
}
}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 (7718 live)
- /api/mcp — endpoint
- /AGENTS.md — agent guide
- /tools/algovigilance__microgram-site-dev-strategy-router/raw.md — this page's Markdown twin