Skip to main content
Glama

Create contact

create_contact

Create and save a personal contact in Microsoft 365/Outlook with names, up to three emails, phone numbers, addresses, company details, notes, and folder placement.

Instructions

Create a personal contact.

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
notesNo
emailsNoUp to three addresses ("jane@contoso.com" or "Jane Doe <jane@contoso.com>")
folderNoContacts folder (default: the main Contacts folder). Accepts a well-known name (inbox, drafts, sentitems/sent, deleteditems/trash, junkemail/junk, archive, outbox), a display name or path such as "Inbox/Projects", or a folder ID from list_folders
companyNo
surnameNoLast name
jobTitleNo
nicknameNo
givenNameNoFirst name
homePhoneNo
categoriesNo
departmentNo
middleNameNo
displayNameNoDisplay name (default "givenName surname")
homeAddressNoPostal address
mobilePhoneNo
businessPhoneNo
officeLocationNo
businessAddressNoPostal address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered, but the description adds nothing beyond that. It does not say what happens with zero identity fields (all 18 params are optional), whether duplicates are merged or rejected, or what the created record looks like. For a mutation tool with 18 optional fields, that silence is a real gap.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but its brevity here reflects under-specification rather than economy. There is no structure to speak of beyond the bare purpose statement.

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

Completeness2/5

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

With 18 optional parameters, nested address objects, no output schema, and 39% schema coverage, the definition is far too thin to guide a correct invocation. An agent gets no guidance on minimum viable fields, defaults, or the shape of the result, all of which the description would need to supply.

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

Parameters2/5

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

Schema description coverage is only 39% across 18 parameters, so the description is expected to compensate and instead says nothing about any field. The schema does document folder, emails, givenName/surname and displayName, but the majority of fields (notes, company, jobTitle, phones, categories, department, officeLocation) carry no meaning beyond their type.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create a personal contact" gives a clear verb plus resource, so an agent knows this is a write operation producing a new contact record rather than a draft, event, or folder. It does not distinguish itself from siblings like create_draft/create_event or clarify what "personal" excludes (e.g. distribution lists), leaving a small differentiation gap.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no mention of update_contact vs create_contact, and no note on duplicate handling or which folder a new contact lands in. The agent must infer the entire call context from the tool name and schema alone.

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