Skip to main content
Glama
Sign In
whodb-cli

whodb-cli

Official
by clidey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

whodb_platform_orgs

Read-onlyIdempotent

List hosted WhoDB organizations visible to the authenticated user to discover valid IDs, slugs, and names before selecting a workspace.

Instructions

List hosted WhoDB organizations visible to the authenticated user.

Use this after whodb login to discover valid organization ids, slugs, and names before selecting a workspace. This tool is read-only. Prefer fields such as ["id", "name", "slug", "selected"] for discovery. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional top-level output fields to include in items
workspaceNoOptional 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

NameRequiredDescriptionDefault
hostNo
orgsYes
countYes
errorNo
itemsNo
scopeNo
fieldsNo
commandsNo
recoveryNo
warningsNo
retryableNo
workspaceNoOptional 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_codeNo
next_stepsNo
request_idNo
setup_statusNo
suggested_toolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.136.0
    • 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"
+}
  2. Addedv0.135.0

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 bar is lower; even so, the description adds real value by explaining that the workspace object is per-call targeting only and does not change defaults. The sentence 'This tool is read-only' merely restates the annotation and does not add information.

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?

Three short sentences, front-loaded with what the tool returns and followed by usage and parameter advice. The 'This tool is read-only' clause duplicates the annotation and is the only real waste.

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 schema descriptions, the description covers ordering (after login), purpose (discover org identifiers), and per-call override behavior. Only minor items like pagination or result limits are absent, which is acceptable given the output schema.

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 baseline is 3; the description earns a step up by recommending specific fields such as ["id", "name", "slug", "selected"] for discovery, which the schema's generic 'Optional top-level output fields' text does not convey. The workspace override semantics are also reinforced in prose.

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 ('List hosted WhoDB organizations') plus the visibility scope ('visible to the authenticated user'). It implies its position ahead of workspace/project selection, so an agent can distinguish it from whodb_platform_projects or whodb_platform_hosts, though it never names those siblings explicitly.

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?

'Use this after whodb login to discover valid organization ids, slugs, and names before selecting a workspace' gives explicit sequencing and preconditions. There is no explicit when-not or named alternative, so it stops short of the top band.

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

Deploy Server

Other Tools