Skip to main content
Glama
henilcalagiya

io.github.henilcalagiya/mcp-apple-notes

create_note

Create a new Apple Note with an HTML formatted title and body, and save it to a specified folder path for organized note-taking.

Instructions

Create a new note with specified name and content.

Supported HTML: , , , , , Best Practices: Use semantic HTML, add tags for spacing, avoid CSS styles Folders: Root level or nested paths (up to 5 levels deep) Limitations: No special chars in name, no complex CSS/JS

Example: name: "Project Report" body: "Status: In ProgressTask 1"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNote title wrapped in <h1> tags (e.g., '<h1>My Note Title</h1>')
bodyYesNote body content with appropriate HTML formatting (e.g., '<p>Content here</p>'). For proper spacing between two sections, use <br>.
folder_pathNoTarget folder path (e.g., 'Work' or 'Work/Projects/2024'). Defaults to 'Notes'Notes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It discloses supported HTML tags, folder depth limits, and name character restrictions, but does not mention idempotency, overwrite behavior, or error handling. The output schema exists, so return values are not required in the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with headings and contains useful examples, but it is somewhat lengthy. While every part adds value, it could be more concise without losing clarity.

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 tool's complexity (3 parameters, output schema present), the description covers creation details, HTML formatting, folder paths, and limitations. It lacks clarity on duplicate behavior and permissions, but overall is fairly 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 description coverage is 100%, providing clear parameter meanings. The description adds value by elaborating on HTML support, example usage, folder path default and nesting limits, which goes beyond the schema's baseline.

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 explicitly states 'Create a new note with specified name and content,' clearly distinguishing it from sibling tools like update_note (update) and create_folder (create a folder, not a note). It also provides specifics about HTML support and folder structure.

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 offers best practices (e.g., using semantic HTML, adding <br> for spacing, avoiding CSS) and explains folder path limitations. While it doesn't explicitly list when not to use, the context from sibling tools and the clear purpose make usage guidelines adequate.

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