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

mcp-apple-notes

by santiago-migoni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_note

Create a new note in Apple Notes with Markdown content. The first line automatically becomes the note title.

Instructions

Crea una nueva nota en Notes.app. El contenido es Markdown; la primera línea se convierte en el título de la nota (así es como Notes.app deriva el título del cuerpo).

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": {
      "content": "<content>"
    },
    "name": "create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesContenido en Markdown. La primera línea será el título.
folderNoCarpeta destino dentro de la cuenta iCloud (default: "Notes"). Debe existir.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It explains the creation and title derivation but does not disclose permissions, side effects, or error handling. Adequate but not rich.

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 efficient sentences, front-loaded with the action, no unnecessary words. Every sentence earns its place.

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 simple tool with 2 params and no output schema, the description covers core behavior and a key nuance (title from first line). It misses mention of return value or multi-account handling, but is largely complete.

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 description coverage is 100%, so baseline is 3. The description's parameter info (Markdown, title derivation) largely repeats the schema, adding no new value beyond the schema.

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 it creates a new note in a specific app (Notes.app) and explains how the title is derived from the first line of content, distinguishing it from sibling tools like update_note or delete_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?

No explicit guidance on when to use vs alternatives, but the creation action is self-explanatory among siblings like list, read, update, delete, search. Implied usage.

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