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

mcp-apple-notes

by santiago-migoni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_note

Replace the full content of an existing Apple Note with new Markdown text, where the first line sets the title.

Instructions

Reemplaza el contenido completo de una nota existente. El contenido es Markdown; la primera línea se convierte en el título.

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

Input Schema

NameRequiredDescriptionDefault
idYesId de la nota a actualizar.
contentYesNuevo contenido completo en Markdown, reemplaza el anterior.

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?

No annotations are present, so the description must convey behavioral traits. It adds one key detail (first line of content becomes title) but does not disclose other aspects like whether the update is reversible, permissions needed, or side effects. The replacement nature is implied but not explicitly labeled as destructive.

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 short sentences, no redundant information, efficient delivery of core purpose and key behavior. Every word serves a purpose.

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 update tool with no output schema and two well-described parameters, the description provides necessary context (Markdown, title extraction). It lacks mention of success/error responses or idempotency, but is sufficient for basic use.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that content is Markdown and explaining the first-line-to-title behavior, which is not in 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 the action ('reemplazar el contenido completo') and the resource ('nota existente'), and distinguishes itself from sibling tools (create, delete, read, list, search) by focusing on replacement of existing content.

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 explicit guidance is provided on when to use this tool versus alternatives, no when-not-to-use conditions, and no mention of prerequisites or context. The sibling tools are listed but not compared.

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