whodb-cli

Official

Overview Schema Source Related Servers Discussions Admin

whodb_platform_status

Read-onlyIdempotent

Report the active hosted login and selected workspace (host, org, project). Confirm session context before calling other platform tools, or pass a workspace to target one call without changing defaults.

Instructions

Report the current hosted WhoDB login and selected hosted workspace.

Requires a prior hosted login with whodb login. Use this before other whodb_platform_* tools to confirm which host, organization, and project are active. 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
`user_id`	No
`commands`	No
`recovery`	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
`request_id`	No
`setup_status`	No
`auto_selected`	No
`saved_default`	No
`session_scope`	No
`default_org_id`	No
`suggested_tools`	No
`default_org_name`	No
`platform_version`	No
`process_override`	No
`default_project_id`	No
`workspace_selected`	Yes
`default_project_name`	No
`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

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the lower bar applies; the description still adds real context beyond them — the login prerequisite and the fact that the workspace argument is per-call and does not mutate defaults. That is the kind of state/authorization context annotations cannot express.

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

Conciseness5/5

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

Three sentences, front-loaded with what it reports, then the prerequisite, then the ordering rule and the optional targeting behavior. No filler and no repetition of schema structure.

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

Completeness5/5

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

An output schema exists, so return values need no explanation; with that burden removed, the description covers purpose, prerequisite, ordering and the optional targeting parameter — everything needed to call this read-only status tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds genuine semantics: the workspace object is a per-call target that does not change saved defaults. It overlaps somewhat with the schema's own note ('Does not change the default host'), which limits it below a 5.

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: 'Report the current hosted WhoDB login and selected hosted workspace.' That is concrete enough to distinguish it from data-access siblings, but it does not differentiate against close cousins in the same family such as whodb_platform_workspace_resolve, whodb_platform_workspace_summary or whodb_platform_workspace_map, which an agent could plausibly confuse it with.

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?

Explicitly states the prerequisite ('Requires a prior hosted login with whodb login') and a clear ordering rule ('Use this before other whodb_platform_* tools'). It stops short of naming an alternative tool or a when-not-to-use condition, so it is strong context rather than full routing guidance.

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

Deploy Server