whodb-cli

Official

Overview Schema Source Related Servers Discussions Admin

whodb_platform_doctor

Read-onlyIdempotent

Checks hosted WhoDB MCP readiness before workflows or when platform tools fail, reporting login status, selected workspace, manifest availability, and actionable warnings.

Instructions

Check hosted WhoDB MCP readiness.

Use this when platform tools fail or before a workflow. It reports login, selected workspace, manifest availability, and actionable warnings. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

Name	Required	Description	Default
`workspace`	No	Optional target for this call only. Omit to use the session default set by whodb_platform_session_use, then process/saved defaults. Discover targets with whodb_platform_hosts, whodb_platform_orgs and whodb_platform_projects.

Output Schema

Name	Required	Description
`host`	No
`email`	No
`error`	No
`scope`	No
`checks`	Yes
`org_id`	No
`commands`	No
`org_name`	No
`recovery`	No
`warnings`	No
`retryable`	No
`workspace`	No	Optional target for this call only. Omit to use the session default set by whodb_platform_session_use, then process/saved defaults. Discover targets with whodb_platform_hosts, whodb_platform_orgs and whodb_platform_projects.
`error_code`	No
`next_steps`	No
`project_id`	No
`request_id`	No
`org_selector`	No
`project_name`	No
`suggested_tools`	No
`platform_version`	No
`project_selector`	No
`workspace_selected`	Yes
`manifest_protocol_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.136.0Oct 23, 2026

addedOutput schema / properties / error_code
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / recovery

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "LikelyCause": {
+      "type": "string"
+    },
+    "NextSteps": {
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    }
+  },
+  "required": [
+    "LikelyCause",
+    "NextSteps"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / retryable
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / suggested_tools

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Addedv0.135.0Oct 15, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only/idempotent/open-world, so the description focuses on the useful extra: it names the categories it inspects (login, selected workspace, manifest availability, actionable warnings) and clarifies the non-destructive nature of per-call targeting ('without changing defaults'). Output schema exists, so return-value detail is not required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with purpose then usage then behavior then parameter note. No filler; a slightly tighter single paragraph would earn a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single optional parameter, full schema coverage, annotations, and an output schema, the description supplies what is needed: what it inspects, when to call it, and that targeting is per-call only. Missing only a pointer to the nearest alternative diagnostics tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema's own workspace description already explains the session-default fallback and points to discovery tools. The description's 'per-call targeting without changing defaults' largely restates that, adding little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource – a readiness/diagnostic check on hosted WhoDB MCP – and enumerates what it reports (login, workspace, manifest, warnings). It is distinguishable from generic siblings like whodb_platform_status or whodb_platform_setup_status only by the word 'MCP', not by any explicit contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this when platform tools fail or before a workflow' gives clear triggering conditions. It does not say when *not* to use it, nor how it differs from the many adjacent health/status tools (setup_status, runtime_readiness, project_health).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server