Revdoku

Account Get

account_get

Read-onlyIdempotent

Get the selected account identity and current connection permissions. account_id selects a granted account; omission uses the credential default. Use account_limits for quotas.

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
`account`	Yes

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."

Changed2 schema fields changedSep 30, 2026

removedInput schema / properties / include_limits

Removed value: -{
-  "default": false,
-  "description": "Value for include limits.",
-  "type": "boolean"
-}

removedOutput schema / properties / limits

Removed value: -{
-  "type": "object"
-}

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / include_limits

Added value: +{
+  "default": false,
+  "description": "Value for include limits.",
+  "type": "boolean"
+}

addedOutput schema / properties / limits
```
Added value: +{
+  "type": "object"
+}
```

AddedSep 30, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description adds that the read returns identity plus connection permissions, which is useful scope information, but says nothing about failure modes when a non-granted account_id is supplied.

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?

Three short sentences, zero filler, with the core purpose front-loaded and the sibling redirect last. Every sentence carries a distinct piece of information.

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 and annotations covering safety, the description does not need to explain return values, and it covers the parameter default correctly. Minor gap: no indication of what happens when the requested account is not granted.

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, including the account_id default and authorization note. The description largely restates those semantics rather than adding new format or constraint detail, so the baseline of 3 applies.

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: 'Get the selected account identity and current connection permissions.' It also names the sibling it is not (account_limits), so an agent can distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

Gives an explicit routing rule ('Use account_limits for quotas') and explains the account_id omission case, which is the main usage decision here. It does not cover when-not-to-use or error/prerequisite conditions beyond the schema's note on Agency authorization.

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.