Skip to main content
Glama
Sign In
Apple Ecosystem MCP

Apple Ecosystem MCP

by abhinavag-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search Reminders

reminders_search
Read-only

Search reminders by title or notes across all lists to locate specific tasks or information quickly.

Instructions

Search reminders by title or notes across all lists.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
include_completedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.9/5.0
Behavior4/5

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

The description adds context beyond the readOnlyHint annotation by specifying that the search covers 'all lists'. This is valuable behavioral information. However, it does not discuss any potential limitations (e.g., indexing delays, maximum results) or return format details.

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 a single sentence that efficiently conveys the tool's purpose with no redundant information. It is appropriately sized and front-loaded.

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?

Given the output schema exists and the tool is relatively simple, the description provides sufficient context about the search scope (across all lists) and the fields searched (title or notes). It lacks details on case sensitivity or partial matching, but these are often inferable from typical search behavior.

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?

With 0% schema description coverage, the description must compensate but only partially explains the 'query' parameter (by mentioning 'by title or notes'). The 'limit' and 'include_completed' parameters are not described at all, leaving the agent to infer their meaning from the schema alone.

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 action (search), resource (reminders), and scope (by title or notes across all lists). It distinguishes itself from sibling tools like reminders_list (which likely lists without search) and reminders_overdue/reminders_today (which are filtered by status/date).

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?

The description implies that this tool is for text-based searching across all lists, but it does not explicitly state when to use it versus other reminder tools like reminders_list, reminders_overdue, or reminders_today. No exclusions or alternative tool names are provided.

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