whodb-cli

Official

Overview Schema Source Related Servers Discussions Admin

whodb_platform_sources

Read-onlyIdempotent

List hosted WhoDB sources for the selected organization and project, optionally targeting a host per call. Read-only results omit credentials and let you choose fields for discovery.

Instructions

List hosted WhoDB sources in the selected organization and project.

Requires a saved login on the target host. Pass workspace {host, org, project}, or omit it to use process/saved defaults. This tool is read-only and never exposes source credentials. Prefer fields such as ["id", "name", "type"] for discovery; request more fields only when needed. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

Name	Required	Description	Default
`fields`	No	Optional top-level output fields to include in items
`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
`count`	Yes
`error`	No
`items`	No
`scope`	No
`fields`	No
`org_id`	No
`sources`	Yes
`commands`	No
`recovery`	No
`warnings`	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
`project_id`	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

A3.7/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 genuine context beyond them: a saved login is required on the target host, and source credentials are never exposed — relevant behavioral facts an agent needs.

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

Conciseness3/5

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

Front-loaded and reasonably short, but the workspace parameter is described twice — once as 'Pass workspace {host, org, project}, or omit it...' and again as 'Accepts workspace {host, org, project} for per-call targeting without changing defaults' — with near-identical content that repeats the schema.

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 and full parameter descriptions, the remaining burden is behavioral context, which is largely met: auth prerequisite, credential safety, and default-resolution order are all stated. A brief note on result cardinality/pagination would complete it.

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 parameters are documented. The description still adds value by recommending a minimal field set (["id", "name", "type"]) for discovery and cautioning against over-requesting, which the schema does not convey.

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 with scope: 'List hosted WhoDB sources in the selected organization and project.' Clear enough to distinguish from source_config, source_content, or source_create, though it doesn't explicitly name those siblings.

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?

Gives targeting guidance ('omit it to use process/saved defaults') and a field-selection preference for discovery, which is useful. However, it never states when to choose this tool over neighbors such as whodb_platform_source_config or whodb_platform_project_resources, so usage is only implied.

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

Deploy Server