Skip to main content
Glama
Sign In
Quolle MCP

Quolle MCP

by Quolle-main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List recent emails

list_emails
Read-only

Retrieve recent email sends newest first, optionally filtered by delivery status or recipient, to check delivery outcomes and recent activity.

Instructions

List recent sends, newest first, optionally filtered by status or recipient. Needs a full-access API key.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 20.
statusNoe.g. delivered, bounced, failed, queued.
recipientNoOnly emails to this address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new context: results are ordered newest-first, the listing is scoped to "recent" sends, and a full-access API key is required. It stops short of describing pagination or the shape of returned entries, which matters for a capped list.

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?

A single sentence with no waste: scope and ordering come first, optional filters second, the auth prerequisite last. Every clause carries information an agent would otherwise have to guess.

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 simple, fully-documented three-parameter list tool with read-only annotations and no output schema, the description covers purpose, filters, ordering, and credentials. The remaining gap is what happens past the result cap and whether any cursor exists, but no such parameter exists in the schema either.

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 carries its own description (default 20, example statuses, recipient addressing), so the schema does the heavy lifting. The description only restates that status and recipient are optional filters and adds no format or semantics beyond that, matching the baseline.

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?

States a concrete verb and resource ("List recent sends") plus ordering ("newest first") and filter axes (status, recipient), so an agent can distinguish it from get_email or send_email by verb alone. It never names a sibling or defines how "recent" is bounded, which keeps it short of a 5.

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 optional filters hint at usage, but there is no explicit when-to-use guidance against siblings like get_email (single message) or list_domains, and no when-not-to-use condition. The API-key note is a prerequisite, not an alternative-selection rule.

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