Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Create contact

create_contact

Create an address book contact for a new person, adding name, emails, phones, addresses, organization, birthday, note, and roles. Search contacts first and update existing records instead.

Instructions

Create a contact in the user’s address book — a person the address book does not yet know, typically because they have never sent mail or shared a calendar event. Holds a name plus optional email addresses, phone numbers, structured postal addresses, an organization, a birthday, a note, and roles: what the person is to the user ("lawyer"), stored only when the user said or confirmed it. Search with search_contacts first: if the person is already known, use update_contact instead so their history stays on one record. The contact syncs to the user’s devices over CardDAV.

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": {
      "name": "<name>"
    },
    "name": "create_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe display name, e.g. "Robin Fairweather".
noteNoFree-text note about the person.
rolesNoWhat the person is to the user ("lawyer", "landlord"), so a later "write to my lawyer" finds them. Only roles the user said or confirmed; never inferred from mail.
emailsNoEmail addresses for this person. A contact does not need one — a name alone is a valid record.
phonesNoPhone numbers for this person.
birthdayNoBirthday as `YYYY-MM-DD`, or `--MM-DD` when the year is unknown.
organizationNoCompany or organization the person belongs to.
postalAddressesNoPostal addresses, structured by component.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent write and not open-world. The description adds meaningful behavior beyond them: the contact syncs to the user’s devices over CardDAV, and roles are stored only when the user said or confirmed them, never inferred from mail. It does not discuss duplicate handling or permission requirements, but it substantially improves behavioral understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads purpose and scope, then provides usage routing and a behavioral note, with no filler. The sentence enumerating optional fields partially repeats the already complete schema, making it slightly longer than necessary, but it remains easy to scan.

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 moderately complex 8-parameter mutation with full schema coverage and annotations, the description covers purpose, prerequisites, and key persistence behavior well. However, with no output schema, it does not state what the tool returns—for example, whether a contact ID or created record is returned—leaving a small gap for an agent that needs the result.

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 description coverage is 100%, so all 8 parameters—including nested email, phone, and postal address fields—are already documented in the schema. The description summarizes the payload and reinforces that a name alone is valid, but adds little format or constraint detail beyond what the schema provides. Baseline 3 applies.

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 ('Create a contact in the user’s address book') and defines creation scope as a person the address book does not yet know, which distinguishes it from update_contact and search_contacts. An agent can identify the operation without opening the schema.

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?

Explicitly instructs to search with search_contacts first and to use update_contact if the person is already known, explaining why (history stays on one record). It names both the alternative tool and the condition that selects it.

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