Skip to main content
Glama

get_contact

Retrieve contact details from Microsoft Outlook by providing a contact ID and account ID using the Microsoft MCP server for efficient management.

Instructions

Get contact details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
contact_idYes

Implementation Reference

  • The handler function decorated with @mcp.tool that implements the logic to retrieve a specific contact by ID using the Microsoft Graph API.
    @mcp.tool
    def get_contact(contact_id: str, account_id: str) -> dict[str, Any]:
        """Get contact details"""
        result = graph.request("GET", f"/me/contacts/{contact_id}", account_id)
        if not result:
            raise ValueError(f"Contact with ID {contact_id} not found")
        return result
  • Entry point that runs the FastMCP server instance, thereby registering and serving all tools defined in tools.py including get_contact.
    mcp.run()
  • Creates the FastMCP instance to which all tools, including get_contact, are registered via decorators.
    mcp = FastMCP("microsoft-mcp")
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. 'Get contact details' implies a read-only operation but doesn't specify whether authentication is required, what format the details are returned in, whether there are rate limits, or what happens if the contact doesn't exist. For a tool with no annotation coverage, this is completely inadequate behavioral information.

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?

The description is extremely concise at just three words. While this results in under-specification, it's not verbose or poorly structured. Every word serves a purpose, and there's no unnecessary repetition or fluff.

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 no annotations, no output schema, and 0% schema description coverage for its 2 required parameters, the description 'Get contact details' is completely inadequate. It doesn't explain what the tool returns, how to use it properly, or provide any context beyond the most basic purpose. For a tool in this context, much more information is needed.

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?

The description provides no information about parameters. With 0% schema description coverage and 2 required parameters (account_id and contact_id), the description doesn't explain what these IDs represent, their format, or how they're used. The description fails to compensate for the complete lack of parameter documentation in the schema.

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 'Get contact details' is a tautology that essentially restates the tool name 'get_contact'. While it indicates the tool retrieves contact information, it doesn't specify what kind of details are retrieved or distinguish this from sibling tools like 'list_contacts' or 'search_contacts'. The purpose is vague rather than specific.

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

Usage Guidelines2/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. There are multiple sibling tools for accessing contact information (list_contacts, search_contacts, update_contact), but the description doesn't indicate this is for retrieving a specific contact by ID versus listing all contacts or searching with filters. No context or prerequisites are mentioned.

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