Skip to main content
Glama
carterlasalle

mac-messages-mcp

by carterlasalle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tool_check_addressbook

Check read access to the local macOS AddressBook database and return a report of permission or path errors. Use when contact lookup fails.

Instructions

Diagnose read access to the local macOS AddressBook database.

This is read-only: it checks whether the server can locate and read local
Contacts/AddressBook data and returns a plain-text diagnostic report with
permission or path errors. It does not modify contacts. Use this when contact
lookup fails; use tool_check_db_access when Messages database reads fail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "tool_check_addressbookOutput",
+  "type": "object"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description clearly states the tool is read-only, does not modify contacts, and returns a plain-text diagnostic report with permission or path errors. Since there are no annotations, the description fully carries the burden of disclosing behavior, and it does so thoroughly.

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 mostly concise and well-structured, but it repeats the read-only and no-modification points across two sentences. This slight redundancy does not harm clarity and keeps the description appropriately short.

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

Completeness5/5

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

For a simple diagnostic tool with no parameters, the description provides all necessary context: what it does, what it returns, when to use it, and when to use an alternative. It is complete and self-contained.

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?

This tool has zero parameters, so the baseline is 4. The description does not need to explain parameters, and the empty schema is fully covered; no additional parameter-specific meaning is required.

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

Purpose5/5

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

The description clearly states the tool diagnoses read access to the local macOS AddressBook database, a specific resource and action. It distinguishes itself from sibling tools by explicitly scoping to AddressBook data, not Messages, making it easy to select correctly.

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

Usage Guidelines5/5

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

The description gives explicit usage guidance: 'Use this when contact lookup fails; use tool_check_db_access when Messages database reads fail.' This directly tells the agent when to choose this tool versus a specific alternative, leaving no ambiguity.

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