Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_scheduled_sends

Read-only

Check scheduled and undo-send messages, newest first. Retrieve ids, status, and send times to find a lost id needed for canceling a send.

Instructions

List items in the local undo-send / scheduled-send queue (from send_email with PROTONMAIL_SEND_DELAY_SECONDS set, or schedule_draft), newest first, 50 per page (returns total/hasMore; page with offset, raise limit for more), including id, status, and sendAt — use this to rediscover the id needed for cancel_send if it was lost with the conversation. Message bodies are shortened and HTML/attachments omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRecords per page, newest first. Default 50.
offsetNoSkip this many records (paging). Check hasMore for more.
statusNoFilter to one status. Omit to list everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.37
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "description": "Records per page, newest first. Default 50.",
+  "type": "number"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Skip this many records (paging). Check hasMore for more.",
+  "type": "number"
+}
  2. Addedv1.17.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so no contradiction. The description adds valuable behavioral details beyond annotations: 'Message bodies are shortened and HTML/attachments omitted', pagination behavior ('returns total/hasMore', 'page with offset'), and the order ('newest first'). This enriches the agent's expectations.

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?

The description is a single dense sentence that front-loads the core purpose and then adds necessary details. It is not overly long and avoids redundancy with the schema. Minor fluff but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with 3 optional params, read-only annotation, and no output schema, the description is complete. It covers the queue's origin, ordering, pagination, returned fields, the use case, and content truncation. An agent has everything needed to invoke it correctly.

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 coverage is 100% and each parameter already has a clear description (limit default, offset for paging, status filter). The description adds a small extra (explicit 'newest first' and 'raise limit for more') but mostly duplicates schema info. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description states a specific verb ('List') and a precise resource ('items in the local undo-send / scheduled-send queue'), and further clarifies the source (from send_email with delay or schedule_draft). It distinguishes from siblings like list_remote_drafts by explicitly noting 'local', and ties to cancel_send. This is clear and unambiguous.

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?

It provides a concrete use case: 'use this to rediscover the id needed for cancel_send if it was lost with the conversation.' It also implicitly differentiates from remote listing by saying 'local'. It doesn't explicitly name alternatives or state when not to use it, but the guidance is strong enough for an agent to decide.

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

Deploy Server

Other Tools