Skip to main content
Glama
Sign In
whodb-cli

whodb-cli

Official
by clidey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

whodb_platform_confirm

Destructive

Confirms and executes a pending hosted WhoDB platform write using a confirmation token after the user approves the preview.

Instructions

Confirm and execute a pending hosted WhoDB platform write.

Use the confirmation_token returned by hosted platform write tools. Tokens expire after 5 minutes. Only call this after the user has approved the pending write preview. The token does not independently prove human approval: the MCP host must enforce approval if that guarantee is required. For uploads, review the full local source path and destination; the file is read at execution time, not snapshotted when the preview is created. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

NameRequiredDescriptionDefault
tokenYesConfirmation token from a previous whodb_query or hosted platform write response
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
rowsYes
errorNo
scopeNo
columnsYes
messageNo
commandsNo
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
next_stepsNo
request_idNo
column_typesNo
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.8/5.0
Behavior5/5

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

Annotations already declare non-readonly, destructive, non-idempotent, open-world behavior, and the description goes further by disclosing token expiry, the fact that the token is not proof of human approval, and that uploads read the file at execution time rather than from a snapshot — a real TOCTOU caveat that changes how an agent should behave.

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?

Front-loaded with the core action, then preconditions, then caveats — a sensible order with no filler. Some sentences carry multiple clauses (approval caveat plus upload caveat), which makes it dense but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, the description need not explain return values, and it covers what is left: sequencing after a write preview, token lifetime, approval semantics, and per-call workspace targeting with a pointer to host/org/project discovery tools. Nothing needed to invoke it safely is missing.

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 the heavy lifting is done structurally. The description still adds meaning beyond the schema: it clarifies where the token comes from and that it is time-limited, and confirms the workspace block is per-call targeting that does not change session defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Confirm and execute a pending hosted WhoDB platform write.' This clearly distinguishes it from whodb_platform_pending (which lists pending writes) and whodb_platform_write_plan (which plans them), so an agent can pick the right tool without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the trigger ('Use the confirmation_token returned by hosted platform write tools'), the precondition ('Only call this after the user has approved the pending write preview'), and a hard timing constraint ('Tokens expire after 5 minutes'). The when-to-call and the sequencing relative to write tools are fully specified.

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