Skip to main content
Glama
carterlasalle

mac-messages-mcp

tool_check_contacts

Retrieve and display contacts from your macOS address book through the Messages app interface.

Instructions

List available contacts in the address book.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for 'tool_check_contacts'. Registered with @mcp.tool() decorator. Lists contacts from AddressBook using get_cached_contacts(), shows count and samples first 10.
    @mcp.tool()
    def tool_check_contacts(ctx: Context) -> str:
        """
        List available contacts in the address book.
        """
        logger.info("Checking available contacts")
        try:
            contacts = get_cached_contacts()
            if not contacts:
                return "No contacts found in AddressBook."
            
            contact_count = len(contacts)
            sample_entries = list(contacts.items())[:10]  # Show first 10 contacts
            formatted_samples = [f"{number} -> {name}" for number, name in sample_entries]
            
            result = [
                f"Found {contact_count} contacts in AddressBook.",
                "Sample entries (first 10):",
                *formatted_samples
            ]
            
            return "\n".join(result)
        except Exception as e:
            logger.error(f"Error checking contacts: {str(e)}")
            return f"Error checking contacts: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists contacts but doesn't reveal any behavioral traits like whether it requires permissions, how it handles errors, or what the output format might be. This is a significant gap for a tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'available contacts' means, how results are returned, or any limitations, which is inadequate for a tool that interacts with data. More context is needed to fully understand its behavior.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and a baseline of 4 is appropriate as it doesn't mislead or omit necessary information in this context.

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 clearly states the action ('List') and resource ('available contacts in the address book'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'tool_check_addressbook' or 'tool_find_contact', which likely have overlapping functionality, so it doesn't achieve full distinction.

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 such as 'tool_find_contact' or 'tool_check_addressbook'. It lacks explicit context, exclusions, or prerequisites, leaving the agent without direction on tool selection.

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

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/carterlasalle/mac_messages_mcp'

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