Skip to main content
Glama

search_contacts

Search local macOS Contacts by name, organization, email, or phone to retrieve matching contact records for on-device lookups.

Instructions

Search macOS Contacts by name, organization, email or phone.

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": "search_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It never says whether matching is substring or exact, whether it is case- or diacritic-insensitive, whether results are ranked, or that the tool requires macOS Contacts permission.

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?

A single short sentence with no wasted words, and the resource and searchable fields are front-loaded. It is terse to the point of under-specification, but there is no filler or redundancy.

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?

For a tool with zero annotation coverage, zero schema descriptions, and no output schema, this description is too thin. An agent knows what to search but not how matching works, what the result shape is, or how 'limit' governs the response.

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 explain both parameters. It does clarify that 'query' is matched against name, organization, email or phone, which is genuine added value, but the 'limit' parameter (default 20, max 100) is never mentioned anywhere.

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?

Uses a specific verb ('Search') and a specific resource ('macOS Contacts'), plus the fields the query matches (name, organization, email, phone). This clearly separates it from list_events, list_reminders, search_notes and the other siblings, though the differentiation is implicit rather than stated.

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?

No when-to-use or when-not-to-use guidance, no stated prerequisites (Contacts access permission), and no mention of what to do if the search returns nothing or too much. The only guidance is the implied notion that this is the contacts-lookup tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.