whodb-cli

Official

Overview Schema Source Related Servers Discussions Admin

whodb_platform_project_delete

Destructive

Deletes a hosted WhoDB project by id, slug, or name, returning a token for explicit confirmation before performing the destructive action.

Instructions

Delete a hosted WhoDB project.

This is destructive. Pass project as id, slug, or name and org when needed for disambiguation. Default mode returns a confirmation token; do not call whodb_platform_confirm until the user explicitly approves the deletion. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

Name	Required	Description
`org`	No	Organization id, slug, or name. Defaults to the selected organization when available.
`project`	Yes	Project id, slug, or name
`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
`error`	No
`scope`	No
`status`	No
`warning`	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
`result_json`	No
`setup_status`	No
`suggested_tools`	No
`confirmation_token`	No
`confirmation_action`	No
`confirmation_expiry`	No
`confirmation_preview`	No
`idempotency_replayed`	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.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is known. The description adds genuinely non-redundant behavior: the confirmation-token gating and user-approval requirement, plus the fact that workspace targeting is per-call only and does not change defaults.

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 with no filler; the destructive warning and confirmation gating are front-loaded where they matter most. Slight redundancy with schema-documented parameter forms keeps it from 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?

With rich annotations, an output schema, and full parameter documentation, the description supplies the one thing structured fields can't: the confirm-token workflow. Complete enough for correct invocation, though sibling differentiation against whodb_platform_delete 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%, so project/org/workspace semantics (id, slug, or name; org for disambiguation; per-call workspace) are already fully documented. The description restates these rather than adding new meaning, which is the expected baseline-3 case.

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 ("Delete a hosted WhoDB project") rather than a generic delete. It does not explicitly name the sibling whodb_platform_delete or source_delete as alternatives, so an agent must infer that this targets hosted projects only.

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?

Clear operational context: it flags destructiveness and prescribes a two-step flow — default mode returns a confirmation token and whodb_platform_confirm must not be called until the user approves. It lacks explicit guidance on when to prefer this over the generic whodb_platform_delete.

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

Deploy Server