Skip to main content
Glama

List the messages scheduled to leave later

list_scheduled_sends

Lists the messages given a "send_at" that have not left yet, soonest first: when each leaves (in the zone of the person you act for), from which address, to whom, the subject and text, and the thread an answer goes into. A message that has left is no longer here but in its thread. One that could not leave stays, with state "failed" and the reason, until it is cancelled.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_scheduled_sends"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoNarrows to the messages leaving from one address, from list_sender_addresses. A mailbox's own address gives all of its messages, those leaving under its aliases included; an alias gives the ones leaving under that name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"Narrows to the messages leaving from one address, from list_sender_addresses."New value: +"Narrows to the messages leaving from one address, from list_sender_addresses. A mailbox's own address gives all of its messages, those leaving under its aliases included; an alias gives the ones leaving under that name."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it delivers real state semantics: sent messages disappear from this list, failed ones persist with a state and reason until cancelled, and ordering is soonest first with times rendered in the acting person's zone. It omits any volume, pagination, or permission expectations for a list that could be long.

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?

Front-loaded with the scope condition and ordering before the enumeration of returned fields, and the closing sentence about failed sends earns its place. The middle enumeration of fields (address, recipient, subject, text, thread) is slightly run-on but compensates for the absent output schema.

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?

For a single optional-filter list with no output schema and no annotations, the definition covers ordering, time zone, field content, and lifecycle states well. Only the pagination/limit question is left unaddressed.

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%, including the mailbox-versus-alias semantics of address, so the baseline is 3. The description adds nothing about the address filter, leaving all narrowing behavior to the schema.

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 plus the defining scope condition: messages with a "send_at" that have not left yet, returned soonest first. It also draws the boundary against the obvious confusion case — a message that has left is found in its thread, not here — so an agent can tell what this list contains without opening the 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 clear conditions for what appears in this list versus the thread alternative, and notes that failed sends remain until cancelled, which implies the cancel path. It stops short of naming cancel_scheduled_send as the action to take on the failed entries it returns.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources