Skip to main content
Glama
carterlasalle

mac-messages-mcp

by carterlasalle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tool_check_db_access

Diagnoses read access to the local macOS Messages SQLite database, verifying the server can locate and query it and reporting any permission or path errors to resolve access issues.

Instructions

Diagnose read access to the local macOS Messages database.

This is read-only: it checks whether the server can locate and query the
Messages SQLite database and returns a plain-text diagnostic report with any
permission or path errors. It requires Full Disk Access for the host app or
terminal. Use this after message reads/searches fail or return permission
errors; use tool_check_addressbook for Contacts/AddressBook access issues.

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_db_accessOutput",
+  "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?

With no annotations provided, the description carries the full burden of behavioral transparency. It explicitly states the operation is read-only, describes the output as a plain-text diagnostic report including permission/path errors, and discloses the Full Disk Access requirement. No contradictions or hidden side effects are present.

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 compact and well-structured, with no redundant or extraneous content. Each sentence serves a distinct purpose: defining the tool, clarifying read-only behavior and output, and providing usage guidance with an alternative.

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 and lack of parameters, the description provides complete context: what it checks, what it returns, what permissions are required, when to use it, and which sibling tool to use instead. The output type (plain-text diagnostic report) is also specified.

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 zero parameters, so there is no parameter-specific information to add beyond the empty schema. The description accurately reflects this by not mentioning any arguments, matching the baseline for 0-parameter tools.

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's purpose with a specific verb ('Diagnose') and resource ('read access to the local macOS Messages database'). It also distinguishes itself from sibling tools by explicitly pointing to tool_check_addressbook for Contacts/AddressBook access issues.

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 explicitly states when to use the tool: after message reads/searches fail or return permission errors. It also names the alternative tool for Contacts/AddressBook issues, leaving no ambiguity about appropriate usage.

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