Skip to main content
Glama

List contacts

list_contacts
Read-only

Retrieve personal Outlook contacts alphabetically with pagination and folder filtering. Browse saved contacts, or use search_people to find people by name, including the organization directory.

Instructions

List personal contacts alphabetically. Use search_people to find people by name, including the organization directory.

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
limitNoContacts to return (default 50)
folderNoContacts folder (default: the main Contacts folder). Accepts a well-known name (inbox, drafts, sentitems/sent, deleteditems/trash, junkemail/junk, archive, outbox), a display name or path such as "Inbox/Projects", or a folder ID from list_folders
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a useful trait beyond that — results are alphabetically ordered — but says nothing about pagination behavior, default page size, or that it only covers the personal contact set rather than the directory.

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 tool's own scope stated first and the sibling routing second. Every sentence earns its place.

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 read-only list tool with a mostly documented schema and no output schema, the definition covers purpose, ordering, and the main alternative. The only real gap is paging guidance (limit/offset), which matters for a list tool but is partly handled by the schema.

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 67%, with limit and folder well documented in the schema while offset carries no description anywhere. The description itself contributes no parameter meaning — it never mentions folder scoping, paging, or the default result count — so the 3 baseline is appropriate.

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?

"List personal contacts alphabetically" gives a specific verb, resource, and ordering, and contrasts itself with search_people which reaches the organization directory. It stops short of clarifying folder scope (main Contacts folder vs other folders), so an agent still has a small ambiguity, but the core purpose is unambiguous.

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?

The description explicitly names the alternative (search_people) and the condition that selects it: looking up people by name, including the organization directory. That implies list_contacts is for browsing your own contacts, though it never states the positive case outright or mentions when not to use it.

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