Skip to main content
Glama

list_contacts

Retrieve and manage Outlook contacts by fetching a specified number of entries linked to an account ID using Microsoft MCP server integration.

Instructions

List contacts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
limitNo

Implementation Reference

  • The handler function for the 'list_contacts' tool, decorated with @mcp.tool for registration. It fetches a list of contacts from Microsoft Graph API for the specified account_id, with optional limit.
    @mcp.tool
    def list_contacts(account_id: str, limit: int = 50) -> list[dict[str, Any]]:
        """List contacts"""
        params = {"$top": min(limit, 100)}
    
        contacts = list(
            graph.request_paginated("/me/contacts", account_id, params=params, limit=limit)
        )
    
        return contacts
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List contacts' reveals nothing about whether this is a read-only operation, requires authentication, has rate limits, returns paginated results, or what format the output takes. For a tool with parameters and no output schema, this is completely inadequate.

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 extremely concise at two words, which could be appropriate if it were informative. However, this brevity results in under-specification rather than efficient communication. It's front-loaded but lacks substance, making it more of a placeholder than a helpful description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 2 parameters, 0% schema coverage, no annotations, no output schema, and multiple sibling alternatives, the description is completely inadequate. It fails to explain what the tool does beyond the name, provides no usage context, and offers no parameter guidance. This leaves the agent with insufficient information to use the tool correctly.

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

Parameters1/5

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

Schema description coverage is 0%, meaning parameters 'account_id' and 'limit' are undocumented in the schema. The description adds no information about what these parameters mean, their expected formats, or how they affect the listing. With 2 parameters and no compensation in the description, this leaves the agent guessing about required inputs.

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

Purpose2/5

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

The description 'List contacts' is a tautology that restates the tool name without adding specificity. It doesn't distinguish this tool from sibling tools like 'search_contacts' or 'get_contact', nor does it specify what kind of listing (e.g., all contacts, filtered by account, paginated). This provides minimal value beyond the name itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'search_contacts' and 'get_contact' available, there's no indication of whether this tool is for bulk listing, filtered searches, or basic retrieval. The agent receives no context about appropriate use cases or exclusions.

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

Related 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/elyxlz/microsoft-mcp'

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