Skip to main content
Glama

manage-contact

List, search, create, update, or delete personal contacts in Outlook. Manage contact details including name, email, phone, company, and notes.

Instructions

Manage personal contacts. action=list (default) lists contacts. action=search searches by name/email. action=get retrieves full details. action=create adds a contact. action=update modifies a contact. action=delete removes a contact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoAction to perform (default: list)
countNoNumber of results (action=list default: 50, action=search default: 25)
skipNoPagination offset for action=list (default: 0). Use the value suggested by the previous page response.
folderNoContact folder ID (action=list)
outputVerbosityNoOutput detail level (action=list/search, default: standard)
queryNoSearch query for name or email (action=search, required)
idNoContact ID (action=get/update/delete, required)
displayNameNoFull name (action=create/update)
firstNameNoGiven name (action=create/update). Maps to Graph `givenName`. If displayName not provided, will be combined with lastName.
lastNameNoSurname (action=create/update). Maps to Graph `surname`.
emailNoPrimary email address (action=create/update)
emailsNoMultiple email addresses (action=create/update). First entry is primary.
mobilePhoneNoMobile phone number (action=create/update)
companyNameNoCompany name (action=create/update)
jobTitleNoJob title (action=create/update)
notesNoPersonal notes (action=create/update)
Behavior1/5

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

The description states 'delete removes a contact', which implies a destructive action, but annotations set destructiveHint: false. This is a clear contradiction. Additionally, the description does not disclose other behavioral traits such as side effects (e.g., irreversible deletion), authorization needs, or rate limits beyond what the annotations already claim (which are contradicted).

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 description is one sentence that front-loads the overall purpose and then lists actions concisely. It avoids unnecessary words, but could benefit from line breaks or bullet points for clarity. It earns its length but is not overly compact.

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?

Given the tool's complexity (16 parameters, 6 actions) and no output schema, the description covers the high-level actions but omits important context like pagination behavior (count/skip only for list), required fields per action (implicit from schema but not restated), return values, error handling, or ordering. It is adequate but not thorough.

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?

With 100% schema description coverage, the input schema already details each parameter's meaning. The description adds marginal value by grouping parameters implicitly under actions but does not provide new semantic insights beyond listing which action each parameter belongs to. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool manages personal contacts and lists six specific actions (list, search, get, create, update, delete), each with a brief explanation. This provides a specific verb-resource mapping and distinguishes it from sibling tools like 'search-people' by specifying 'personal contacts'.

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 implies when to use each action (e.g., 'action=get retrieves full details') but provides no explicit guidance on when not to use this tool or alternatives like 'search-people'. No exclusions or context for tool selection are given, leaving the agent to infer usage from action names.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/littlebearapps/outlook-assistant'

If you have feedback or need assistance with the MCP directory API, please join our Discord server