Revdoku

Client Account Create

client_account_create

Create a separate client account sharing the Pro Agency plan. 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.
`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 bucket 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.

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.9/5.0

Behavior4/5

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

Annotations only declare write/idempotency/destructive flags. The description adds real behavioral context beyond them: an explicit authorization requirement tied to the Agency owner's connection, and the scoping caveat that account_id 'does not change the credential's default account.' It stops short of describing failure modes or duplicate-name behavior.

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?

Four short sentences, front-loaded with the action and scope, then the parameter clarification, then the authorization and account_id caveats. Every sentence carries information, though the account_id sentence is slightly redundant with the schema entry.

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, return values need not be explained, and all three parameters are fully described in the schema. The description covers the key auth prerequisite and account scoping for a mutation, leaving only edge cases like duplicate accounts or failure handling unaddressed.

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 description coverage is 100%, so both parameters are already documented in the schema, which sets the baseline at 3. The description adds modest elucidation, clarifying that name is the account name while client_name separately identifies the client person or business, but no format or constraint detail beyond the schema.

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?

The description states a specific verb and resource plus scope: 'Create a separate client account sharing the Pro Agency plan.' An agent immediately understands this provisions a distinct client account under the agency's plan, and the sibling bucket_*/revdoku_* tools are clearly a different domain, so differentiation is not needed.

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 gives a precondition ('Requires the Agency owner's explicitly authorized connection') and guidance on the optional account_id ('Pass the Agency account_id when needed'), which is useful context. However, it never states when to create a client account versus another account type, nor any when-not condition or alternative, leaving usage largely implied.

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.