Skip to main content
Glama

Create Contact

create_contact

Create a Microsoft 365 contact with name, email, phone, job title, and company details so users can save new people directly from an AI assistant.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
emailNoEmail address
surnameNoLast name
job_titleNoJob title
given_nameYesFirst name
company_nameNoCompany name
mobile_phoneNoMobile phone number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive mutation, so the description is not contradicting them, but it adds nothing beyond them. It omits useful behavioral context for a create operation: duplicate handling, required permissions, and what happens on conflict. With no output schema, the description leaves the response shape unknown as well.

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 clause is front-loaded and wastes no words, but for a six-parameter mutation tool it is undersized to the point of being under-specified rather than genuinely concise.

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?

For a write tool with no output schema and only hint-level annotations, the description should at least cover required input, duplicate behavior, or result semantics. None of that is present, leaving the agent to call a mutating endpoint on name alone.

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% across all six parameters, including the required given_name, so the schema carries parameter meaning on its own. The description adds no further semantics (e.g., format expectations or which fields are commonly paired), so the baseline of 3 applies.

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

Purpose3/5

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

"Create a new contact" names a specific verb and resource, which is enough to place it apart from delete_contact, get_contact, and update_contact by name alone. However, it is a near-verbatim restatement of the title and tool name, and adds no scope detail (e.g., what a contact contains or where it is stored), so it sits at the minimum-viable level.

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?

There is no when-to-use guidance, no mention of prerequisites, and no explicit routing to siblings such as update_contact or create_draft. The agent must infer usage entirely from the name.

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