Skip to main content
Glama

Revdoku

by com.revdoku
OverviewDiscussionsAdmin

Mailbox List

mailbox_list
Read-onlyIdempotent

List visible storage mailboxes with incoming-email activity and archive/delete eligibility. Pass query to filter by email address or ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional case-insensitive contains-filter on the authorized mailbox email address or ID.
reasonNoOptional 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_idNoOptional 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
NameRequiredDescriptionDefault
mailboxesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Optional case-insensitive contains-filter on mailbox title."New value: +"Optional case-insensitive contains-filter on the authorized mailbox email address or ID."
    • changedOutput schema / properties / mailboxes / items / properties / email / description
      Previous value: -"Accepted email activity. Creation and write-authorized include_email reads also return the full address and receiving state. Activity is not a delivery cursor. Use mailbox_email_list to poll for arrivals."New value: +"Email activity and the address permitted by the connection. Creation and write-authorized include_email reads also return receiving settings. Activity is not a delivery cursor. Use mailbox_email_list to poll for arrivals."
    • removedOutput schema / properties / mailboxes / items / properties / title
      Removed value: -{
-  "type": "string"
-}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the scoping word 'visible' (only authorized mailboxes) and lists returned field categories, which is modest extra context, but says nothing about pagination, ordering, or result 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 tight sentences with the listing scope front-loaded and the parameter hint second. No filler or redundancy.

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 explained, and the description adequately conveys what is listed and the filter option. It omits any indication of how many mailboxes return or ordering, a minor gap for a list tool.

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 all three parameters (query, reason, account_id) are already documented in the schema. The description's 'filter by email address or ID' merely restates the query schema rather than adding format or matching details beyond it.

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 (list) and resource (visible storage mailboxes) plus the scoping qualifier 'visible' and the fields surfaced (incoming-email activity, archive/delete eligibility). This separates it implicitly from mailbox_get and mailbox_email_list, though no sibling is named explicitly.

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 sentence 'Pass query to filter by email address or ID' gives a usage hint for one parameter but offers no when-to-use/when-not-to-use guidance and never names the alternative sibling (e.g., mailbox_get for a single mailbox). Usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Revdoku toolsInspect
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.

Resources