whodb-cli

Official

Overview Schema Source Related Servers Discussions Admin

whodb_platform_workspace_resolve

Read-onlyIdempotent

Resolve a workspace host, org, and project to canonical IDs and verify the active login for per-call targeting without changing saved defaults.

Instructions

Resolve workspace {host, org, project} to canonical IDs and verify the login. Does not switch or save defaults. 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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds meaningful context beyond them: it verifies the login and confirms no defaults are mutated, which clarifies the operation's side-effect surface. It stops short of describing output shape, but an output schema exists.

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?

It is short and front-loaded with the core action. However, the non-default behavior is stated twice ('Does not switch or save defaults' and 'without changing defaults'), which is slight redundancy in an otherwise tight description.

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?

With an output schema present, the description needn't explain return values, and it covers the key behavior (canonical ID resolution, login verification, no default mutation). Sufficient for a single-parameter read tool, though naming discovery siblings would round it out.

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 description coverage is 100%, including per-field descriptions for host, org, and project, so the schema carries the parameter semantics. The description only restates the workspace tuple, adding no format or resolution details beyond what the schema provides — baseline 3 is appropriate.

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

Purpose5/5

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

The description states a specific verb and resource ('Resolve workspace {host, org, project} to canonical IDs') plus a secondary effect ('verify the login'). It also distinguishes itself from the sibling whodb_platform_session_use by explicitly stating it does not switch or save defaults.

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?

It gives clear context for use: per-call targeting of a workspace without changing session defaults. The exclusions ('Does not switch or save defaults') implicitly route the agent away from session_use, but no sibling is named explicitly and discovery tools (hosts/orgs/projects) are only mentioned in the schema, not the description.

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

Deploy Server