Skip to main content
Glama

graph_create_contact

Create a new Outlook contact with name, email, phone, company, and job title via Microsoft Graph. Use it to add people to your contacts list.

Instructions

Create an Outlook contact. Requires the Contacts.ReadWrite permission.

Empty fields are omitted from the created contact.

Args: given_name: First name of the contact. surname: Last name of the contact. email: Primary email address. mobile_phone: Mobile phone number. company_name: Company the contact works for. job_title: Job title of the contact.

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

Input Schema

NameRequiredDescriptionDefault
emailNo
surnameNo
job_titleNo
given_nameYes
company_nameNo
mobile_phoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the required permission scope and that empty fields are omitted rather than written as blank values, but says nothing about the return value (whether the created contact with its id comes back), duplicate handling, or which contact folder receives the new record.

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 opening sentence is front-loaded and the two behavioral notes follow immediately. The Args list is justified by 0% schema coverage, though it partially restates property names whose meaning is already evident.

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

Completeness3/5

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

For a create mutation with no annotations and no output schema, the definition covers permissions and empty-field handling but leaves the response shape, folder placement, and failure/duplicate behavior unspecified. It is adequate to construct a call but not to predict its outcome.

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 0%, so the Args block is the only documentation and does cover all six parameters. The additions are thin because most property names are self-explanatory; the one genuinely non-obvious semantic, that empty strings are dropped rather than persisted, is stated in the body and materially affects how the caller should pass the defaulted parameters.

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 an Outlook contact" names a specific verb and resource, which cleanly separates it from graph_update_contact and graph_delete_contact in the surrounding toolset. It stops short of explicitly contrasting itself with those siblings, so it lands just under the top mark.

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

Usage Guidelines3/5

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

The description supplies a real prerequisite (Contacts.ReadWrite permission), which tells the agent whether it can call at all. It offers no when-to-use versus when-not guidance and does not point at graph_update_contact for existing contacts, so the selection logic stays implicit.

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