whodb-cli

Official

Overview Schema Source Related Servers Discussions Admin

whodb_platform_bundle_import_plan

Read-onlyIdempotent

Plan how a project bundle would import into a selected hosted project, including conflict handling, before executing the actual import.

Instructions

Plan how a project bundle would import into the selected hosted project.

This MCP tool is intentionally plan-only. Use the CLI resources import --yes command for execution after review. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

Name	Required	Description
`prefix`	No	Optional prefix added to imported resource names
`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.
`bundle_json`	Yes	Project bundle JSON from whodb_platform_bundle_export or resources export
`rename_conflicts`	No	Create unique names for resources that conflict with existing resources
`overwrite_conflicts`	No	Update resources that conflict with existing resources

Output Schema

Name	Required	Description
`plan`	No
`error`	No
`scope`	No
`counts`	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

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/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 safety profile is covered; the description still adds real value by stating the tool never mutates and by telling the agent how execution is actually performed. It does not describe what the plan output contains, but an output schema exists to carry that.

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 tight sentences: purpose first, then the plan-only constraint, then the execution path and targeting note. No filler, and the most decision-relevant fact (plan-only) is front-loaded.

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?

An output schema exists so return format need not be explained, and the description covers the plan/execute split and per-call workspace targeting. The only gap is that it doesn't distinguish itself from the sibling bundle_import tool an agent will also see in the list.

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 the schema already documents bundle_json, prefix, rename_conflicts, overwrite_conflicts, and the nested workspace object. The description only restates the workspace targeting behavior already captured in the schema, adding no syntax 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?

States a specific verb and resource ('Plan how a project bundle would import') plus the explicit scope limitation ('intentionally plan-only'), which clearly separates it from an executing import. It does not name the sibling whodb_platform_bundle_import, even though that tool's presence makes the distinction worth spelling out.

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?

Gives a concrete when-to-use (plan, review) and a when-not/alternative (execution happens via the CLI 'resources import --yes' command). The routing is clear, but it points to a CLI command rather than clarifying the relationship to the very similar MCP sibling, leaving some ambiguity an agent may stumble on.

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

Deploy Server