Skip to main content
Glama
epinethrone

icloud-mcp

by epinethrone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

mail_find_correspondent

Read-only

Find people you have emailed with by name, address, company, or domain. Get the address they actually use and message counts each way when contacts search fails.

Instructions

Find people the owner has exchanged email with by approximate name, address or company, with the address they really use and message counts each way.

Use when: contacts_search_contacts finds nobody, or you need the address a person actually writes from. Not for saved contacts (use contacts_search_contacts) or for messages from someone (use mail_search_messages with from_address). Parameters: every word of query must match a name, address part or domain; misspellings match as 'similar'. limit is clamped to 1-25. search_all_history=false scans the newest ~3,000 INBOX and ~1,500 Sent messages; true scans both whole. Behavior: read-only; reads only From, To and Cc headers in INBOX and Sent, never bodies or other folders. The scan is cached 10 minutes, so the newest mail may be missing. Exact matches rank first. Returns: {query, returned, matches, scanned}; each match has name, address, also_written_as, messages_from_them, messages_to_them, last_contact and match ('exact' or 'similar'). 'similar' means only similar in spelling or sound: ask the owner to confirm which person they meant before sending or inviting anyone. No match gives a hint: retry with search_all_history=true, or ask the owner. Errors: an empty query is refused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax people to return (1-25).
queryYesName, email address or company/domain of a person you have emailed with: 'laura', 'l.jansen', 'acme'. Misspellings are tolerated.
search_all_historyNofalse = the most recent ~3,000 received and ~1,500 sent messages (fast). true = the whole mailbox (slower, up to ~20 seconds).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mail_find_correspondentDictOutput",
-  "type": "object"
-}New value: +null
  2. Changed5 schema fields changedv0.7.0
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • changedInput schema / properties / query / description
      Previous value: -"Name, email address or company/domain of a person you have emailed with: 'laura', 'l.jansen', 'acme'. Misspellings and variant spellings are tolerated."New value: +"Name, email address or company/domain of a person you have emailed with: 'laura', 'l.jansen', 'acme'. Misspellings are tolerated."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / search_all_history / title
      Removed value: -"Search All History"
    • removedInput schema / title
      Removed value: -"mail_find_correspondentArguments"
  3. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Adds rich behavior beyond the readOnlyHint and openWorldHint annotations: it reads only From/To/Cc headers in INBOX and Sent, never bodies or other folders, uses a 10-minute cache, may miss newest mail, ranks exact matches first, and warns that 'similar' matches require owner confirmation. It also documents no-match hints and the empty-query refusal.

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?

Despite covering purpose, usage, parameters, behavior, returns, and errors, it is tightly structured under front-loaded labels. Each sentence contributes necessary operational detail for a complex search tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

Given the absence of an output schema and the tool's non-trivial search semantics, the description fully covers return fields, match types, caching limitations, scanning scope, and error behavior. Nothing critical for correct invocation appears missing.

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 coverage is already 100%, but the description adds material parameter semantics: every query word must match a name, address part, or domain; misspellings match as 'similar'; limit is clamped to 1-25; and search_all_history toggles between recent-cache scanning and full-mailbox scanning with approximate volumes.

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: find people the owner has exchanged email with, by approximate name/address/company, plus what is returned. It explicitly distinguishes itself from contacts_search_contacts and mail_search_messages, so an agent can route correctly without opening sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: use when contacts_search_contacts finds nobody, or when you need the address someone actually writes from. It also names when not to use it and which sibling to use instead for saved contacts or messages from a person.

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