Local MCP

Microsoft 365 Create Contact

m365_create_contact

Destructive

Use this when the user wants a new contact added to their Microsoft 365 / Outlook contacts. Give at least a name or an e-mail. Needs the account connected with scopes_for: ["contacts"].

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

Input Schema

Name	Required	Description
`name`	No	The name shown for the contact (default: first and last name).
`notes`	No	Notes.
`title`	No	Job title.
`emails`	No	Up to 3 e-mail addresses.
`mobile`	No	Mobile phone.
`phones`	No	Up to 2 business phones.
`account`	No	Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.
`company`	No	Company.
`confirm`	No	Ignored; kept for older clients.
`surname`	No	Last name.
`given_name`	No	First name.

Output Schema

Name	Required	Description
`name`	No
`fields`	No
`status`	Yes
`account`	No	The email (UPN) of the Microsoft 365 account this call used.
`contact`	No
`created`	Yes
`message`	No
`previous`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the write/open-world profile is covered. The description adds genuinely new operational context: the account must be connected with the 'contacts' scope. It omits duplicate handling and what happens when a matching contact already exists, which matters for a create tool flagged destructive.

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?

Three short sentences, with the invocation trigger front-loaded ahead of the input minimum and the auth prerequisite. The inline 'scopes_for: ["contacts"]' notation is slightly awkward in prose but does not waste space.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The description supplies the trigger, the minimum input and the auth requirement — enough to call it correctly, though a note on duplicate creation would round it out.

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 coverage is 100% across all 11 parameters, so the schema carries the field-level meaning. The description does add one useful constraint beyond the schema: 'Give at least a name or an e-mail', which matters because the required array is empty and nothing in the schema enforces a minimum payload.

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?

States a specific verb and resource ('new contact added to their Microsoft 365 / Outlook contacts'), which cleanly separates it from m365_update_contact, m365_get_contact and m365_list_contacts. It does not name any sibling explicitly, so differentiation is inferred from the verb rather than stated.

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?

'Use this when the user wants a new contact added' gives an explicit trigger condition, and the scope prerequisite tells the agent what must be true before calling. It stops short of exclusions, e.g. what to do when the contact already exists (update vs. create) or when to prefer m365_search_contacts first.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.