Skip to main content
Glama
carterlasalle

mac-messages-mcp

by carterlasalle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tool_check_contacts

Return a small sample of cached contacts with names and phone numbers to verify AddressBook data is accessible. Use this to confirm contact lookup is populated or to diagnose permission/database issues.

Instructions

List a small sample of contacts available from AddressBook.

This is read-only: it loads cached local contact names and phone numbers and
returns a count plus sample entries, structurally neutralized and wrapped in
<untrusted-mcp-output>. Requires Contacts/AddressBook permission. Use this to
confirm contact lookup is populated; use tool_find_contact to resolve a
specific person, and tool_check_addressbook to diagnose permission or
database access failures.

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_contactsOutput",
+  "type": "object"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Discloses read-only nature, loads cached data, returns count plus sample entries, wraps in untrusted output, and requires Contacts/AddressBook permission. Since no annotations are provided, this description carries the full burden and does so well.

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?

Description is appropriately sized, with a clear main statement followed by useful details on behavior, permissions, and alternatives. No extraneous content.

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?

Given the tool's simplicity, the description covers purpose, behavior, output, permissions, and relationship to sibling tools, making it complete.

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?

Tool has zero parameters; the empty schema fully documents this, and the description adds no parameter details, which is appropriate. Baseline 4 for zero params.

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?

Clearly states it lists a small sample of contacts from AddressBook, and differentiates from sibling tools by referencing tool_find_contact and tool_check_addressbook.

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?

Explicitly states when to use it (confirm contact lookup is populated) and when to use alternatives (tool_find_contact for a specific person, tool_check_addressbook for diagnosing permission/database issues).

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