Skip to main content
Glama
Sign In
apple-productivity-mcp

apple-productivity-mcp

by gambadio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

apple_contacts_search

Read-onlyIdempotent

Find contacts by name or organization substring in Apple Contacts, returning summaries rather than full contact details.

Instructions

Read-only: find contacts by name or organization substring. Returns summaries, not all contact details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "apple_contacts_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so 'Read-only' is largely redundant. However, 'Returns summaries, not all contact details' is genuinely valuable behavioral context given there is no output schema, and it warns the agent that full details require another call.

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?

Two tight sentences with no waste, and the safety/scope note is front-loaded ahead of the return-shape caveat.

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

Completeness4/5

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

For a read-only search tool with rich annotations and no output schema, the description covers scope and return shape adequately. The remaining gap is pagination behavior for limit/offset, which the description does not address.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all three parameters. It explains only 'query' (substring match against name/organization); limit and offset are left completely undocumented in both schema and description.

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 gives a specific verb ('find'), resource ('contacts'), and the matching semantics ('by name or organization substring'). This clearly distinguishes it from apple_contacts_get (fetch one contact) and apple_contacts_list_groups.

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

Usage Guidelines3/5

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

Usage is implied by the substring-matching search phrasing, but there is no explicit statement of when to prefer this over apple_contacts_get or when not to use it. No prerequisites or alternatives are named.

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