whodb-cli

Official

Overview Schema Source Related Servers Discussions Admin

whodb_platform_workflow_list

Read-onlyIdempotent

Lists persisted hosted WhoDB workflow plans for the selected workspace, letting you target a host, organization, or project per call without changing session defaults.

Instructions

List persisted hosted WhoDB workflow plans for the selected workspace. 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
`plan`	No
`error`	No
`plans`	No
`scope`	No
`status`	No
`message`	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
`suggested_tools`	No
`confirmation_token`	No
`confirmation_expiry`	No
`confirmation_required`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.136.0Oct 23, 2026
- changedOutput schema / properties / recovery / type
```
Previous value: -[
-  "null",
-  "object"
-]New value: +"object"
```
- changedOutput schema / properties / suggested_tools / type
```
Previous value: -[
-  "null",
-  "array"
-]New value: +"array"
```
Addedv0.135.0Oct 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds that plans are 'persisted' and that per-call workspace targeting does not change defaults, which is genuinely useful context, but that same default-preservation point is repeated from the schema. Nothing about result volume or paging is added, though 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?

Two sentences, front-loaded with what the tool does. The second sentence is not wasteful but overlaps materially with the workspace schema description, so it is slightly redundant rather than earning full marks.

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?

A read-only list tool with an output schema, fully documented parameters, and annotations covering safety and world scope. The description supplies the essential purpose, so an agent can call it correctly; only the sibling differentiation is left implicit.

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% and the workspace object documents host/org/project, the 'omit to use session default' behavior, and the discovery siblings. The description's second sentence merely restates the per-call targeting already in the schema, adding no format or precedence detail beyond it.

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?

Specific verb plus resource: 'List persisted hosted WhoDB workflow plans' clearly says what the tool returns and its scope. It does not name any sibling, so the agent must infer the split from workflow_get (single plan), workflow_plan (create plan), and workflow_apply (execute).

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

Usage Guidelines3/5

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

Usage is only implied by the verb 'list'; there is no statement of when to prefer this over workflow_get or workflow_recipe, and no prerequisites or exclusions. The fallback chain for the workspace default lives 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