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

mcp-apple-notes

by santiago-migoni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_notes

Search Apple Notes by text in title and content, excluding recently deleted notes. Supports substring matching and result limits up to 200.

Instructions

Busca notas por texto (case-insensitive, substring) en título y contenido. No incluye notas en Recently Deleted.

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
queryYesTexto a buscar.
limitNoCantidad máxima de resultados (default 50, máximo 200).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries full responsibility. It discloses key behaviors: case-insensitive substring search, scope (title and content), and exclusion of Recently Deleted. Missing details like ordering or pagination are minor gaps.

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, front-loaded with the core action, and contains no unnecessary words. It efficiently conveys purpose and key constraints.

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

Completeness3/5

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

The description covers basic purpose and behavioral traits but lacks details expected in search tools (e.g., result ordering, pagination, return format). Given no output schema, it leaves some ambiguity for an agent.

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

Parameters3/5

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

Schema coverage is 100%, so parameters are documented in the schema. The description adds no new semantic information beyond the schema; it reiterates the search text and limit. Baseline 3 is appropriate.

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 searches notes by text with case-insensitive substring matching in title and content, and excludes Recently Deleted. This distinguishes it from siblings like list_notes (which lists all) and read_note (single note).

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 usage for text search but does not explicitly state when to use this tool versus alternatives (e.g., list_notes, read_note). No guidance on when not to use or prerequisites is 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