Revdoku

Revdoku Status

revdoku_status

Read-onlyIdempotent

Check Revdoku email and file access, account identity, granted accounts and connector version. Pass account_id per call to select a granted account; omission uses the credential account. Respect account restrictions and returned support guidance. Reconnect if tools are missing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`mcp`	No
`user`	No
`account`	No
`accounts`	No
`features`	No
`connection`	No
`default_account_id`	No
`hosted_client_safety`	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 30, 2026

removedOutput schema / properties / onboarding

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "recommended_next_step": {
-      "type": "string"
-    },
-    "state": {
-      "enum": [
-        "empty_account",
-        "no_visible_buckets",
-        "active"
-      ],
-      "type": "string"
-    },
-    "suggested_projects": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "id": {
-            "type": "string"
-          },
-          "summary": {
-            "type": "string"
-          },
-          "title": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}

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"
+  ]
+}

Changed1 schema field changedSep 23, 2026
- removedOutput schema / properties / publishing
```
Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
```

Changed7 schema fields changedSep 13, 2026

addedOutput schema / properties / account / properties / account_kind

Added value: +{
+  "enum": [
+    "standard",
+    "agency",
+    "client"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / account / properties / agency_account

Added value: +{
+  "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"
+  ]
+}

addedOutput schema / properties / account / properties / client_name

Added value: +{
+  "description": "Client person or business; null when not set. Never infer it from the account name or owner.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / account / properties / kind

Added value: +{
+  "description": "Compatibility alias for account_kind.",
+  "enum": [
+    "standard",
+    "agency",
+    "client"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / account / properties / name / description

Added value: +"Account name, separate from the client person or business."

addedOutput schema / properties / accounts

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "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"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / default_account_id

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedSep 8, 2026

addedInput schema / properties / account_id

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

First observedAug 17, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the response carries granted accounts, connector version and support guidance, and that account restrictions must be respected — useful, but no detail on failure modes or what 'support guidance' actually contains.

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 verb and the scope of what is checked, with no filler. The trailing sentences on restrictions and reconnecting are terse and slightly opaque, but they are not wasted.

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 no explanation here, and both optional parameters are documented. For a low-complexity, read-only, two-optional-parameter status tool, the description covers what an agent needs; only the sibling-routing gap keeps it from full marks.

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%; both account_id and reason are fully documented in the schema, including the pointer to revdoku_status.accounts and the 'never infer from a mailbox id' rule. The description restates the account_id omission default but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

'Check' + a concrete list of what is checked (email and file access, account identity, granted accounts, connector version) makes the purpose unambiguous. It is clearly distinguishable from the mailbox_* mutation siblings, though it never names account_get/account_list, which cover adjacent territory.

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 the key calling convention (pass account_id per call, omit to use the credential default) and one conditional remedy ('Reconnect if tools are missing'), which is genuine usage guidance. However it never states when to call this versus account_get or account_list, nor that this should be called first to discover valid account ids.

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.