Detsky Mir Selfcheck
detmir_selfcheckVerify Detsky Mir endpoint connectors after installation or when results look wrong, returning a tri-state verdict: success, drift, or inconclusive.
Instructions
Probe every Detsky Mir endpoint family and report a tri-state verdict.
success — everything answered with the expected shape.
drift_detected — an endpoint answered but the payload no longer parses;
the connector needs updating. inconclusive — transport or geo blocking
prevented a verdict, which says nothing about the parsers.
Run it after install and whenever results look wrong.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "detmir_selfcheck"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| checks | No | Per-endpoint-family results. | |
| status | No | Overall verdict: success, drift_detected, or inconclusive. | |
| connector | No | Connector name. | detmir |
| process_id | No | OS process id. | |
| tool_count | No | Number of MCP tools registered on the server. | |
| cache_stats | No | TTL cache counters for this process. | |
| config_loaded | No | Whether settings loaded successfully from env/defaults. | |
| server_version | No | Connector server version. | |
| server_started_at | No | Server start timestamp (UTC ISO-8601). |