Skip to main content
Glama

Create contact

create_contact

Record a person in MailFathom's contact book with name, addresses, preferred address, and note. If an address is already held by another contact, the write is refused and that contact is returned.

Instructions

Records a person in MailFathom's own contact book: their name, every address they use, which one is preferred, and an optional note. Writes to local state only — nothing is sent to a mail server or to anybody else, and no mail is touched. Calling twice with the same person records them once and then answers addressHeldByAnotherContact, because one address belongs to one contact across the whole book; look that contact up with get_contact rather than writing a second record. Ask the person you are acting for before writing somebody down.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoWhat to record about this person, up to 4000 characters, or omit for none. Line breaks and tabs are kept. This is free text about a third party: write only what the person you are acting for asked to be recorded.
addressesYesEvery mail address this person uses, at most 32 entries of at most 320 characters each. Two spellings of one address are stored once and the first spelling is the one kept, but both still count towards the 32. An address another contact already holds refuses the write.
displayNameYesThe name to record for this person, as it should be read back, up to 256 characters. Characters that render as nothing are refused.
preferredAddressYesThe address to use when addressing this person without naming which of theirs to use. Must be one of addresses; state it even where the record names a single address, because nothing picks one for the owner.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYesHow the write ended. written means the book holds the record; notFound means no contact of that identifier is in the book; addressHeldByAnotherContact means one of the addresses already belongs to somebody else, named by addressHolderContactId; contactWasCollected means the record came from mail that arrived rather than from somebody writing it down, so promote_contact it before amending it; alreadyAsserted means a promotion had nothing left to do.
contactNoThe record as the book now holds it, or null. Only a write whose record you supplied publishes one: create_contact, update_contact, add_contact_address, and remove_contact_address answer with the record when they succeed, while promote_contact answers with the outcome alone and is read back with get_contact.
addressHolderContactIdNoThe identifier of one contact that already holds an address this write claimed, or null when that is not what stopped it. Read that contact with get_contact to see who it is; a record may clash with more than one person, and this names one of them.
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which only indicate non-read-only, non-idempotent, non-destructive), the description discloses critical behaviors: writes go to local state only, no mail is sent or touched, duplicate calls result in an addressHeldByAnotherContact error because each address is globally unique, and user consent is required before writing. These details significantly expand the agent's understanding of side effects and constraints.

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 concise yet information-dense, with each sentence serving a clear purpose: purpose, scope, duplicate behavior, and consent. It front-loads the core purpose in the first sentence and then adds necessary caveats without fluff. No wasted words.

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 tool's complexity (global uniqueness, duplicate handling, consent requirement) and the fact that an output schema exists, the description is complete. It covers the write scope, the failure mode for duplicates, the alternative tool to use, and the need for user consent. No significant behavioral gaps remain that aren't already answered by the schema or annotations.

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?

The input schema already covers all four parameters with detailed descriptions (100% coverage), so the baseline is 3. The description does add high-level context (e.g., 'every address they use' and 'optional note') but does not introduce new parameter-level semantics beyond what the schema already states, such as the uniqueness constraint on addresses or the requirement that preferredAddress must be one of addresses. It reinforces but does not substantially augment the schema.

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 opens with a specific verb and resource: 'Records a person in MailFathom's own contact book' and enumerates the exact fields (name, addresses, preferred address, optional note). It clearly distinguishes from sibling tools like get_contact, update_contact, and delete_contact by explicitly stating that it creates a record and advising to look up existing contacts with get_contact instead of writing a second record.

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?

The description gives explicit when-to-use and when-not-to-use guidance: it states that duplicate writes should be avoided and directs the agent to 'look that contact up with get_contact rather than writing a second record.' It also provides context that the tool writes to local state only, so it is appropriate for adding a person to the contact book without touching mail, and it even includes a consent requirement ('Ask the person you are acting for').

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Krzysztof318/MailFathom'

If you have feedback or need assistance with the MCP directory API, please join our Discord server