Skip to main content
Glama

List the messages started and not sent

list_compose_drafts

Lists the messages begun on the account addresses and never sent, last written first, with their recipients, subject, text and files. These are unsent texts, not the answers Iris wrote for review, which list_drafts holds.

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_compose_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoNarrows to the messages started on one address, from list_sender_addresses. A mailbox's own address gives all of its messages, those started under its aliases included; an alias gives the ones started 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 started on one address, from list_sender_addresses."New value: +"Narrows to the messages started on one address, from list_sender_addresses. A mailbox's own address gives all of its messages, those started under its aliases included; an alias gives the ones started 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?

With no annotations supplied, the description carries the full burden and does disclose the ordering guarantee (last written first) and the content of each returned item (recipients, subject, text, files). It does not state pagination, result limits, or that listing requires no special permissions, which leaves some operational gaps for a collection endpoint.

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?

Two tightly packed sentences with no filler, and the scoping/sibling caveat is placed after the core definition where it belongs. The phrasing "messages begun on the account addresses" is slightly abstract but still readable.

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-parameter list tool with no output schema, the description compensates well by enumerating the returned fields and the sort order. The only missing piece is pagination/volume behavior, which matters for a collection endpoint that could return many unsent messages.

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% and the address parameter already documents the mailbox-vs-alias narrowing behavior, so the description adds no parameter detail beyond the schema. Baseline 3 applies when 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?

States a specific verb and resource ("Lists the messages begun on the account addresses and never sent"), adds ordering (last written first) and returned fields (recipients, subject, text, files), and explicitly names the sibling it is not (list_drafts). An agent can distinguish this from list_drafts 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 exclusion — these are unsent texts, not the reviewable answers held by list_drafts — which is the main confusion risk given the sibling name. It stops short of a positive when-to-use trigger (e.g., "use when the user asks about unfinished or abandoned emails"), so routing context is clear but not fully spelled out.

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