Skip to main content
Glama
Sign In
sch-mail

sch-mail

by weirdapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sch_list_mail

List recent messages from a mailbox folder with subject, sender, date, and attachment indicators. Filter by date to review relevant emails.

Instructions

List recent messages with subject, sender, date, and attachment indicators.

Each result's "id" is the message's IMAP UID: stable across calls, unlike a sequence number, and the value every msg_id parameter expects.

Args: folder: Mailbox folder (default: INBOX) top: Max messages to return (default: 20, max: 100) since: Only messages after this date (YYYY-MM-DD). Default: last 30 days. account: Account key in credentials.json (e.g. "personal" or "work"). Default: the account named by "default" in that file.

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": "sch_list_mail"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
sinceNo
folderNoINBOX
accountNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral context: the 'id' is an IMAP UID that is stable across calls (unlike a sequence number) and is the value every msg_id parameter expects, plus which credentials file/account governs the call. It omits rate limits, ordering guarantees, or empty-result behavior, but the UID stability note is genuinely useful information not available elsewhere.

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?

The primary action is front-loaded in sentence one, the important UID caveat follows, and the Args block is a compact per-parameter reference. No sentence is redundant or padded.

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 read-only listing tool with an output schema present, the description need not explain return shape, and it correctly focuses on parameters and the id semantics that link output to other tools. Minor gaps remain (no statement about empty results or what happens if the folder is missing), but nothing essential for a correct call is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does for all four parameters: folder default INBOX, top default 20 with a 100 maximum, the YYYY-MM-DD format and 30-day default for since, and the account key convention with its default resolution rule. This is exactly the information the bare schema lacks.

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 first sentence gives a specific verb and resource ('List recent messages') plus the concrete fields returned (subject, sender, date, attachment indicators), which distinguishes it from sch_get_mail and sch_search_mail implicitly. It never names the alternatives, so an agent must infer the routing, but the purpose itself is unambiguous.

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 default 30-day 'since' window and 'recent messages' framing imply when this listing tool is appropriate versus a search, but there is no explicit when-to-use or when-not-to-use statement and no sibling is named. Guidance is implied rather than stated.

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