Skip to main content
Glama

search_notes

Search Apple Notes by title to find specific notes in a local macOS notes library. Set a result limit to control how many matching notes are returned.

Instructions

Search Apple Notes by title.

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_notes"
  }
}

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?

With no annotations supplied, the description carries the full behavioral burden, yet it discloses only that matching is by title. It says nothing about case sensitivity, substring versus exact matching, whether note bodies are searched, default result ordering, or what fields come back per note.

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 front-loaded sentence with zero filler; the scope qualifier arrives immediately. Its brevity is efficient rather than padded, though the terseness tips into under-specification elsewhere.

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 search tool with no annotations, no output schema, and zero schema description coverage, the definition leaves too much unstated: result shape, ordering, and pagination behavior are all absent. Only the matching field is conveyed.

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 nothing documents either parameter in structured form. The phrase "by title" gives some meaning to query, but limit (default 20, max 100) is never explained in terms of ordering, truncation, or how to request more results, so half the parameters remain opaque.

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?

"Search Apple Notes by title" names a specific verb (search) and resource (Apple Notes) and even narrows the matching field to title. It is not a tautology, though it does nothing to distinguish itself from siblings such as create_note, which is a write path rather than a query.

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?

There is no guidance on when to reach for this tool versus any alternative, no prerequisites, and no statement of what happens with an empty or unmatched query. The agent must infer usage entirely from the name and the single required parameter.

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