Skip to main content
Glama

graph_list_contacts

Lists a user's saved Outlook contacts from a selected or default folder, with paging options for large contact collections.

Instructions

List the user's saved Outlook contacts.

Args: top: Maximum number of contacts to return (default 25, maximum 50). folder_id: Contact folder ID. Empty lists the default contacts folder. skip: Number of items to skip before returning results (default 0). Graph returns at most 50 per call, so page by raising skip in steps of top. compact: Whether to return only the identifying fields instead of the full record (default false). Use it to page through large collections cheaply. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

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

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
compactNo
folder_idNo
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/5.0
Behavior4/5

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

With zero annotations the description must carry the behavioral burden, and it does disclose key traits: a server-side page cap of 50 despite a larger top, a paging loop via skip/next_link, next_link overriding other paging arguments, and include_next_link switching the envelope between a bare list and {items, next_link}. It omits the read-only/safety framing and any permission requirements, which is the remaining 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?

The purpose line is front-loaded as a single sentence, followed by a structured Args block where each entry adds new information. It is longer than average but nearly every clause (page cap, override precedence, return envelope) earns its place; minor tightening is possible around the compact description.

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 six-parameter, all-optional paging tool with no output schema and no annotations, the description covers invocation, paging strategy, and return shape. What is left underspecified is the content of the returned record and which fields 'identifying fields' in compact mode actually includes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and it does for all six parameters: defaults for top, skip, compact, and include_next_link; the meaning of an empty folder_id; and the precedence rule that next_link overrides the other paging arguments. This is meaning an agent could not recover from the bare schema.

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?

States a specific verb and resource: 'List the user's saved Outlook contacts', which distinguishes it from graph_list_contact_folders (folders, not contacts) and the other graph_list_* siblings. It stops short of naming any alternative explicitly, so it is clear but not sibling-differentiating in the strongest sense.

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?

Usage is implied rather than prescribed: 'Use it to page through large collections cheaply' guides the compact flag, and the skip advice ('page by raising skip in steps of top') gives a concrete paging strategy. There is no when-to-use/when-not-to-use framing, no mention of a search or filter alternative, and no stated prerequisites for the call.

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

Deploy Server

Other Tools