Skip to main content
Glama
Sign In
whodb-cli

whodb-cli

Official
by clidey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

whodb_platform_pending

Read-onlyIdempotent

List pending hosted WhoDB platform writes awaiting confirmation and recover their confirmation tokens to preview changes before approval.

Instructions

List pending hosted WhoDB platform writes awaiting confirmation.

Use this to recover confirmation tokens returned by hosted platform write tools. Preview output contains metadata and changed field names only; it never includes credential or secret values. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

NameRequiredDescriptionDefault
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
errorNo
scopeNo
pendingYes
recoveryNo
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
request_idNo
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by scoping the return content: preview output carries metadata and changed field names only and never exposes credential or secret values. It omits how long confirmation tokens remain valid, which is material for a tool whose sole job is recovering them.

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 front-loaded sentences with no filler: purpose, usage, output-safety, then parameter note. The final workspace sentence is partially redundant with the schema's own description of per-call targeting, which is the only wasted effort.

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 shape need not be re-explained, and the single parameter is fully documented. The description covers purpose, invocation trigger, and output safety adequately. The remaining gap is token lifetime / staleness behavior, which matters given this tool exists specifically to hand back confirmation tokens.

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 coverage is 100% and the nested workspace object already documents each of host/org/project, their fallback order, and the discovery siblings. The description's "Accepts workspace {host, org, project} for per-call targeting without changing defaults" largely restates what the schema already says, so the baseline of 3 is appropriate.

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 (list) and resource (pending hosted platform writes awaiting confirmation), plus the secondary function of recovering confirmation tokens. It is distinguishable from the massive sibling set by the 'awaiting confirmation' framing, though it never names whodb_platform_confirm, the obvious follow-up sibling, so the boundary is inferred rather than stated.

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 to recover confirmation tokens returned by hosted platform write tools" gives an explicit, actionable trigger for calling it. It stops short of the complementary guidance — e.g. that retrieval should be followed by whodb_platform_confirm, or when to skip this and re-run the write tool — so the workflow context is clear but incomplete.

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