Revdoku

Account Limits

account_limits

Read-onlyIdempotent

Read effective mailbox and file-storage quotas for the selected account. account_id selects a granted account; omission uses the credential default.

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
`usage`	No
`limits`	Yes
`account_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields 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."

removedOutput schema / properties / usage / properties / bucket_creations
```
Removed value: -{
-  "type": "object"
-}
```
addedOutput schema / properties / usage / properties / mailbox_creations
```
Added value: +{
+  "type": "object"
+}
```

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / usage

Added value: +{
+  "properties": {
+    "bucket_creations": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

AddedSep 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the useful nuance that quotas are 'effective' (i.e., resolved/aggregated values rather than raw settings) and restates the default-account fallback. It says nothing about who may read quotas or what the returned limits represent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the core capability front-loaded before the optional-parameter note. Every clause conveys something actionable and nothing is repeated for padding.

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 read-only/idempotent profile is fully covered by annotations plus a 100%-documented schema. What remains thin is access context — the description doesn't note that reading quotas for client accounts requires Agency authorization beyond the schema's brief mention. For a simple two-optional-parameter read tool this is close to complete.

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 account_id and reason are already documented in the schema, including the client-account authorization caveat and the no-secrets guidance for reason. The description's account_id sentence largely repeats the schema's 'Omit for the credential's default account' wording and omits reason entirely. Baseline 3 applies when the schema carries the parameter burden.

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 and resource ('Read effective mailbox and file-storage quotas') with a clear scope ('for the selected account'). None of the siblings (account_get, account_list, mailbox_get) expose quotas, so it is naturally distinguished even without naming an alternative. It stops short of explicitly routing away from a sibling, which keeps it at 4 rather than 5.

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?

The second sentence explains account selection ('account_id selects a granted account; omission uses the credential default'), which is usage-relevant but reads as parameter semantics rather than when-to-use guidance. There is no explicit statement of when to choose this over account_get or mailbox_get for account or storage information. Usage is implied by the resource name only.

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.