Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

list_contacts

Retrieve personal Outlook contacts from the authenticated user's address book and optionally filter by name or email to find specific contacts.

Instructions

List personal Contacts from the authenticated user's Outlook address book. Optionally filter by name or email.

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

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of contacts to return (default: 50, max: 999)
skipNoNumber of contacts to skip (for pagination)
searchNoSearch string to filter contacts by name or email

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'List' signals a read-only operation and the address-book scoping tells the agent whose data is returned. It does not disclose pagination behavior, default result size, permission/auth requirements, or what fields each contact contains, leaving meaningful behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the resource and scope front-loaded before the optional filtering note. Every clause carries information.

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?

For a simple, no-required-parameter read tool with a fully documented schema and no output schema, the description covers who the contacts belong to and how to filter them. The remaining gap is the shape of returned contact data, which is minor at this complexity.

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 three parameters (top, skip, search) are already documented in the schema. The description's mention of filtering by name or email adds only marginal meaning beyond the schema's own 'search' description, so the baseline of 3 applies.

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 uses a specific verb and resource ('List personal Contacts') and scopes it to the authenticated user's Outlook address book, which implicitly separates it from distribution groups and contact folders in the sibling set. It stops short of naming those alternatives explicitly, so it is clear but not fully differentiated.

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 the use case (enumerating personal contacts, with an optional name/email filter) but never states when to prefer this over list_contact_folders or list_distribution_groups, nor any exclusions. An agent must infer routing from the resource name alone.

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