Revdoku

Revdoku Dashboard Link

revdoku_dashboard_link

Read-onlyIdempotent

Return a stable dashboard link for mailboxes or connector access. The user signs in normally; the link grants no access.

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.
`redirect_path`	No	Internal Revdoku path to open, for example /mailboxes, /account/access, or /mailboxes/view?id=bkt_...	/mailboxes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`guidance`	No
`dashboard`	No

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

changedInput schema / properties / redirect_path / default
```
Previous value: -"/buckets"New value: +"/mailboxes"
```

changedInput schema / properties / redirect_path / description

Previous value: -"Internal Revdoku path to open, for example /buckets, /account/access, or /buckets/view?id=bkt_..."New value: +"Internal Revdoku path to open, for example /mailboxes, /account/access, or /mailboxes/view?id=bkt_..."

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

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context that annotations cannot express: the link requires normal user sign-in and 'grants no access', which correctly frames it as a navigation aid rather than a credentialed access token. It stops short of noting link expiry or scope limits.

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 short sentences with zero filler. The core purpose is front-loaded and the security clarification follows immediately where it is most useful.

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 a 100%-covered schema, full annotations and an output schema, the description need not explain return values or parameter formats. It covers identity and security semantics adequately; the only shortfall is the absence of explicit routing guidance against sibling tools.

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 reason, account_id and redirect_path are already documented in the schema, including the account-authorization caveat and example redirect paths. The description adds nothing about parameters, which is acceptable at this coverage level and matches the baseline of 3.

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?

The description names a specific verb and resource: 'Return a stable dashboard link' and scopes it to 'mailboxes or connector access'. An agent immediately understands this produces a navigable URL rather than performing mailbox operations. It does not explicitly contrast itself with a sibling, but no sibling performs a comparable function, so differentiation is not a real gap.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives such as revdoku_status, nor any preconditions or exclusions. 'For mailboxes or connector access' merely restates the resource rather than describing a triggering scenario, so usage is only weakly 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.