Skip to main content
Glama
Sign In

Busymail

by app.busymail
OverviewDiscussionsAdmin

List sent mail

list_sent

List mail the user has sent, newest first, with recipients, subject, date and snippet. Useful for checking what the user has already told someone before drafting or summarising. Narrow by date with after and before, each optional on its own.

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

Input Schema

NameRequiredDescriptionDefault
afterNoOnly mail sent from this date onwards, as YYYY-MM-DD. INCLUSIVE: the date itself is included, from midnight. Optional on its own: you may give after, before, both, or neither.
limitNoMaximum messages to return (1-100, default 20).
beforeNoOnly mail sent strictly before this date, as YYYY-MM-DD. EXCLUSIVE: the date itself is excluded entirely, so for a single day pass the NEXT day here - one day is after: 2026-07-05, before: 2026-07-06. Optional on its own: you may give after, before, both, or neither.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden: it discloses ordering, returned fields, and that date bounds are independently optional, which implies a read-only listing. It does not state permissions, pagination/limit interaction, or what an empty result means, so gaps remain for a no-annotation tool.

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?

Three front-loaded sentences with no filler; purpose, use case, and filtering appear in that order. The final clause about optional bounds duplicates the schema and is the one mildly wasteful element.

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?

No output schema, so it correctly names the returned fields, and it covers the only non-obvious behavior (date bounds are independently optional). For a three-parameter read tool this is nearly complete, missing only pagination/volume expectations.

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 the schema already spells out inclusive/exclusive date semantics and the limit range in detail. The description's "narrow by date with after and before, each optional on its own" only restates schema content, so baseline 3 applies.

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 ("List mail the user has sent") plus ordering (newest first) and returned fields (recipients, subject, date, snippet). An agent can distinguish this from search or list_feed without opening any 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 a concrete when-to-use condition: "checking what the user has already told someone before drafting or summarising." It stops short of naming an alternative such as search or list_feed or stating when not to use it, so it is clear context but not full routing guidance.

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

All Busymail 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