Skip to main content
Glama
henilcalagiya

io.github.henilcalagiya/mcp-apple-notes

update_note

Verify a note's ID and current name, then update its title and body with HTML content.

Instructions

Update an existing note by its primary key ID with AppleScript verification.

Required: note_id, note_name, new_name, and new_body parameters Supported HTML: , , , , , Best Practices: Use semantic HTML, add tags for spacing, avoid CSS styles Security: AppleScript verifies ID and name match before updating

Example: note_id: "p1234" note_name: "Current Note Title" new_name: "Updated Report" new_body: "Status: CompleteDone"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYesPrimary key ID of the note to update (e.g., 'p1234')
note_nameYesCurrent name of the note to verify and update
new_nameYesNew note title wrapped in <h1> tags (e.g., '<h1>Updated Title</h1>')
new_bodyYesNew note body content with appropriate HTML formatting (e.g., '<p>Updated content</p>') For proper spacing between two sections, use <br>.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description adds behavioral context: AppleScript verifies ID and name match before updating. However, it lacks details on error handling, idempotency, or side effects, which are important for a mutation tool.

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?

The description is well-structured with a clear first sentence, then grouped information on requirements, HTML support, best practices, security, and an example. While slightly verbose, it front-loads key info.

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 existence of an output schema, the description covers the tool's purpose, input constraints, HTML formatting, and security verification. For a tool with 4 parameters and specific formatting needs, this is sufficiently complete.

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%, but the description adds value beyond the schema by specifying requirements (required), providing an example with concrete values, and explaining HTML formatting rules. This helps the agent understand correct parameter usage.

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 'Update an existing note by its primary key ID with AppleScript verification', specifying the verb (update), resource (note), and distinctive verification step. It distinguishes from sibling tools like create_note and 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists required parameters and provides an example, making the usage context clear. It implicitly differentiates from siblings by focusing on updating, but does not explicitly state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/henilcalagiya/mcp-apple-notes'

If you have feedback or need assistance with the MCP directory API, please join our Discord server