Revdoku

Client Account Create

client_account_create

Create a separate client account within an authorized agency. name is the account name; optional client_name identifies the client person or business separately. Requires the Agency owner's explicitly authorized connection. Pass the Agency account_id when needed; this does not change the credential's default account.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Account name.
`reason`	No	Optional reason for this action. AI agents should include a short purpose for intentional reads and changes when known. Do not invent a reason or include secrets, file contents, or transcripts.
`account_id`	No	Optional account id from revdoku_status.accounts for this call only. Omit for the credential's default account. Client accounts require explicit Agency authorization; never infer an account from a mailbox id.
`client_name`	No	Client person or business name. Omit when unknown.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`account`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedInput schema / properties / account_id / description

Previous value: -"Optional account id from revdoku_status.accounts for this call only. Omit for the credential's default account. Client accounts require explicit Agency authorization; never infer an account from a bucket id."New value: +"Optional account id from revdoku_status.accounts for this call only. Omit for the credential's default account. Client accounts require explicit Agency authorization; never infer an account from a mailbox id."

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / reason

Added value: +{
+  "description": "Optional reason for this action. AI agents should include a short purpose for intentional reads and changes when known. Do not invent a reason or include secrets, file contents, or transcripts.",
+  "maxLength": 2000,
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed3 schema fields changedSep 13, 2026

addedInput schema / properties / client_name

Added value: +{
+  "description": "Client person or business name. Omit when unknown.",
+  "maxLength": 100,
+  "type": "string"
+}

changedInput schema / properties / name / description

Previous value: -"Name value."New value: +"Account name."

addedOutput schema / properties / account / properties

Added value: +{
+  "account_kind": {
+    "enum": [
+      "standard",
+      "agency",
+      "client"
+    ],
+    "type": "string"
+  },
+  "agency_account": {
+    "description": "Parent agency only when this credential can access it. Null does not make a client independent.",
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "type": [
+      "object",
+      "null"
+    ]
+  },
+  "client_name": {
+    "description": "Client person or business; null when not set. Never infer it from the account name or owner.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "id": {
+    "type": "string"
+  },
+  "kind": {
+    "description": "Compatibility alias for account_kind.",
+    "enum": [
+      "standard",
+      "agency",
+      "client"
+    ],
+    "type": "string"
+  },
+  "name": {
+    "description": "Account name, separate from the client person or business.",
+    "type": "string"
+  }
+}

AddedSep 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this a non-read, non-destructive write; the description adds meaningful behavioral context by stating the Agency owner authorization requirement and clarifying that passing account_id does not change the credential's default account. No contradiction with annotations.

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 tight sentences, front-loaded with the create action and immediately following with the key parameter distinctions. No filler, though the final clause is slightly dense.

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 values need not be described, and the auth precondition plus parameter disambiguation are covered. Little is missing for correct invocation, though guidance on irreversible/duplicate behavior and alternatives would fully close the gap.

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 baseline is 3, but the description adds real semantics beyond the schema: it distinguishes name (account name) from client_name (client identity) and explains the account_id override is per-call and does not rebind the default credential.

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?

Specific verb+resource: 'Create a separate client account within an authorized agency,' which cleanly separates it from read-only siblings like account_get/account_list. The scope ('separate client account') is stated, though no sibling is named as an alternative.

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?

It states a clear precondition ('Requires the Agency owner's explicitly authorized connection') and clarifies use of account_id, but gives no explicit when-to-use vs. when-not guidance and names no alternative even though mailbox_create sits among the siblings.

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

All Revdoku tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.