Skip to main content
Glama

create_contact

Create a contact with name, email, phone, address, birthday, job title, or organization, and block duplicate names or emails unless duplicates are explicitly allowed.

Instructions

Create a contact. Give 'given_name' or 'family_name' or 'organization'. Before it saves, it looks for a contact with the same full name or the same email. If it finds one, it refuses with AMBIGUOUS and shows the contact, unless 'allow_duplicate' is true. Notes are not supported.

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

Input Schema

NameRequiredDescriptionDefault
emailsNoList of {label, value} objects with the email address.
phonesNoList of {label, value} objects with the phone number.
birthdayNoBirthday. Date as 2026-11-12, or --11-12 when the year is not known.
addressesNoList of postal addresses. Each has at least one of street, city, state, postal_code, country.
job_titleNoJob title.
given_nameNoFirst name.
family_nameNoLast name.
organizationNoCompany or organization.
allow_duplicateNotrue to save even when a contact with the same name or email exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false. The description goes well beyond by disclosing the pre-save duplicate lookup, its matching keys (full name or email), the exact failure code AMBIGUOUS, and the returned existing contact on collision. That is precisely the behavioral detail an agent needs before attempting a create.

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?

Four short sentences, front-loaded with the action and the hard requirement, then the duplicate behavior, then a scoping limitation. No filler and no repetition of schema text.

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 9-parameter mutation tool with no output schema, the description covers the precondition, the failure mode, and the bypass flag, which is most of what matters. It does not say what a successful call returns (e.g., whether the new contact identifier comes back), leaving the agent to infer the response shape.

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%, so the baseline is 3, but the description adds meaning the schema does not carry: the schema marks required as empty, while the description imposes an at-least-one-of given_name/family_name/organization rule. It also gives allow_duplicate concrete semantics (bypass the duplicate refusal rather than merely 'save anyway'). Remaining parameters such as emails/phones/addresses get no extra treatment beyond 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 ("Create a contact") and immediately constrains it with the minimum identity fields required. An agent can distinguish it from sibling creators like create_note or create_event purely from the resource and the explicit note "Notes are not supported."

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 states a precondition (supply given_name, family_name, or organization) and the escalation path (set allow_duplicate when a same-name/same-email match should still be saved). It does not name a sibling such as update_contact for the case of modifying an existing person, so guidance is clear but not fully routing.

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