Skip to main content
Glama
Sign In
multi-mail-mcp

multi-mail-mcp

by claygeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search Mail

search_mail

Search across configured Gmail and Microsoft 365 accounts using provider-specific query syntax. Returns recent messages if no query provided.

Instructions

Search one account or all configured accounts. Gmail uses Gmail search syntax. Microsoft 365 uses Graph message search syntax.

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

Input Schema

NameRequiredDescriptionDefault
accountNoOptional local account alias.
providerNoOptional provider filter.
queryNoSearch query. If omitted, returns recent messages.
maxResultsNoMaximum results per account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0-alpha.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions that omitting query returns recent messages, which is helpful. However, it does not disclose rate limits, result ordering, pagination, or whether the operation modifies data.

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 description is two sentences, front-loading the main purpose (search mail) and adding concise details about syntax. No wasted words.

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?

The description omits details about the output format or fields returned. Given that output schema is absent and sibling tools like get_thread suggest structured results, more information about return values would improve completeness.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds meaning beyond schema by clarifying that the 'account' parameter can be omitted to search all accounts and by explaining provider-specific syntax for 'query'.

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?

The description clearly states the tool searches mail across one or all accounts, specifying syntax differences for Gmail and Microsoft 365. This distinguishes it from sibling tools like send_mail or create_draft.

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?

The description provides context on when to use the tool (searching mail) and mentions provider-specific syntax. It does not explicitly state when not to use it or list alternatives, but the purpose is clear enough.

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