Skip to main content
Glama
Sign In
cfu_mail

cfu_mail

by MrShurukan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_messages

Read-only

Find emails by date range, sender, subject, folder, or unread status, returning newest UIDs first with pagination to continue through large result sets.

Instructions

Search by YYYY-MM-DD dates (inclusive since, exclusive before), sender or subject.

Returns newest UIDs first. Pass next_before_uid as before_uid to continue. Preserve account_id, folder, uidvalidity and uid for reading each result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_id": "<account_id>"
    },
    "name": "search_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
beforeNo
folderNoINBOX
senderNo
subjectNo
account_idYes
before_uidNo
unread_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds real behavioral value beyond that: results are ordered newest UID first, and pagination is driven by the returned before_uid value. It omits permission/rate-limit context but is well above the annotation baseline.

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?

Three short lines, zero filler, with the primary capability front-loaded and pagination notes following. Every sentence carries operational 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, schema-undocumented tool with no output schema, the description leaves notable gaps: no mention of limit, unread_only, or the folder scoping behavior. The 'next_before_uid' name it references is not present in the input schema, which could briefly confuse an agent about where that value comes from.

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 0% across 9 params, so the description must carry the load. It clarifies the date format and inclusivity for since/before, the role of before_uid, and the need to carry account_id/folder/uidvalidity/uid forward, but says nothing about limit (default 30), unread_only, or the folder default of INBOX.

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 description names a specific verb (search) and resource (messages) and enumerates the filter facets (date range, sender, subject), so the agent knows exactly what it retrieves. It does not explicitly contrast with the sibling read_message, though the closing line about preserving identifiers 'for reading each result' implicitly routes to that tool.

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?

It gives concrete usage context: date semantics (inclusive since, exclusive before) and pagination continuation via before_uid. It stops short of explicit when-not guidance or naming alternatives like list_folders/read_message as the escape hatch for other needs.

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