Skip to main content
Glama

manage-contact

Perform CRUD operations on Outlook contacts: list, search, create, update, and delete contact information via the Outlook MCP server.

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)
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)
emailNoPrimary email address (action=create/update)
mobilePhoneNoMobile phone number (action=create/update)
companyNameNoCompany name (action=create/update)
jobTitleNoJob title (action=create/update)
notesNoPersonal notes (action=create/update)
Behavior2/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description includes 'delete removes a contact', which suggests destructive potential. This creates ambiguity, though not a direct contradiction. The description adds minimal behavioral context beyond annotations, such as default actions and basic parameter usage, but fails to address permissions, rate limits, or mutation effects adequately.

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 front-loaded with the tool's purpose and efficiently lists actions in a single, well-structured sentence. Every phrase contributes to understanding the tool's scope, though it could be slightly more polished for readability. There's no wasted text, making it appropriately concise.

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 (12 parameters, multiple actions) and lack of output schema, the description provides a basic overview but lacks details on return values, error handling, or integration with sibling tools. Annotations cover some aspects, but for a multi-action tool, more contextual guidance would improve completeness.

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 documents all 12 parameters thoroughly. The description adds value by mapping parameters to actions (e.g., 'query' for 'action=search'), but this is redundant with schema details. It meets the baseline for high schema coverage without significantly enhancing parameter understanding.

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 clearly states the tool manages personal contacts through six specific actions (list, search, get, create, update, delete), providing a comprehensive verb+resource statement. However, it doesn't differentiate this contact management tool from sibling tools like 'search-people' or 'manage-category', which might have overlapping domains, so it doesn't reach the highest score.

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 usage by listing actions with brief context (e.g., 'action=list lists contacts'), but it doesn't explicitly state when to use this tool versus alternatives like 'search-people' or provide exclusions. The guidance is functional but lacks strategic direction for tool selection.

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-mcp'

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