Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

contacts

Create, search, update, and delete Outlook contacts and contact folders. Use it to look up people by name, email, or company, and to manage contact details and addresses.

Instructions

Manage Outlook contacts: list, search, get, create, update, delete contacts and folders

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": {
      "operation": "<operation>"
    },
    "name": "contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of results
skipNoNumber of results to skip
queryNoSearch query
selectNoFields to select
orderByNoField to order by
surnameNoLast name
birthdayNoBirthday (ISO 8601)
folderIdNoContact folder ID
jobTitleNoJob title
nickNameNoNickname
contactIdNoContact ID (for get, update, delete)
givenNameNoFirst name
operationYesThe operation to perform
categoriesNoCategories
departmentNoDepartment
homePhonesNoHome phone numbers
middleNameNoMiddle name
companyNameNoCompany name
displayNameNoDisplay name
homeAddressNoHome address
mobilePhoneNoMobile phone number
searchFieldsNoFields to search in
personalNotesNoPersonal notes
businessPhonesNoBusiness phone numbers
emailAddressesNoEmail addresses (string or array)
officeLocationNoOffice location
businessAddressNoBusiness address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it never discloses that create/update/delete are mutating, whether deletion is permanent or recoverable, what happens to contacts when a folder is deleted, or what permissions are needed. For a mega-tool that can destroy data, this is a substantial gap.

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?

A single sentence with zero filler, front-loaded with the resource and the operation set. It is efficient, though its brevity is partly under-specification rather than disciplined concision.

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 27 parameters, nested address and email objects, eight operation modes, and no output schema or annotations, this definition is far too thin to guide correct invocation. It never explains mode-specific parameter requirements or what the operations return.

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%, so all 27 parameters are documented in the schema itself, establishing a baseline of 3. The description adds no extra meaning about parameter interactions, such as which fields are required for create versus which apply only to search or how searchFields relates to query.

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?

The description names a specific resource (Outlook contacts) and enumerates the concrete operations: list, search, get, create, update, delete, plus folders. That is a clear verb+resource statement an agent can match against a request. It stops short of distinguishing this from siblings like directory or search, which also surface people data.

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 or when-not-to-use guidance, and no hint about choosing between this tool, directory, or search for people lookups. The operation names restate what the schema's enum already lists, so the agent gets no routing help beyond what structured data provides.

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