Skip to main content
Glama

create_note

Create new Apple Notes entries directly from AI agents. Automate note-taking by connecting Claude, Cursor, or Windsurf to macOS via Pilot MCP integration.

Instructions

Create a new note in Apple Notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:82-86 (registration)
    Tool registration loop that registers 'create_note' along with all other tools. Each tool is registered with the MCP server using server.tool() with a generic stub handler that returns a message directing users to install the full macOS binary.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
      }));
    }
  • server.js:34-34 (registration)
    Definition of 'create_note' in the TOOLS array with its description 'Create a new note in Apple Notes'. This is where the tool name and description are defined before being registered in the loop.
    ["create_note", "Create a new note in Apple Notes"],
  • Import statements and server initialization. Imports the MCP SDK (McpServer, StdioServerTransport) and zod for schema validation, then creates the server instance.
    #!/usr/bin/env node
    /**
     * Minimal MCP stub for Glama inspection.
     * Lists all Pilot MCP tools so Glama can detect them.
     * The real server is a native macOS binary.
     */
    const { McpServer } = require("@modelcontextprotocol/sdk/server/mcp.js");
    const { StdioServerTransport } = require("@modelcontextprotocol/sdk/server/stdio.js");
    const { z } = require("zod");
    
    const server = new McpServer({ name: "pilot-mcp", version: "2.2.0" });
Behavior2/5

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

With no annotations provided, the description carries the full burden but only specifies the target platform (Apple Notes). It fails to disclose what content the note contains (apparently empty given zero parameters), return values, side effects, or permissions required.

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, efficient six-word sentence with zero redundancy. Given the tool's simplicity, this length is appropriate and front-loaded.

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?

While the description covers the basic operation, it is minimally viable for a creation tool. It omits what the created note contains (empty?), what identifier or confirmation is returned (no output schema exists), and behavioral side effects.

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?

Per the rules, zero parameters establishes a baseline of 4. The description neither adds nor subtracts value regarding parameters since none exist to document.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (Create) and resource (a new note in Apple Notes), and sufficiently distinguishes from siblings like read_note, list_notes, and other create_* tools (reminder, calendar, etc.) by specifying the Apple Notes platform.

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?

The description provides no guidance on when to use this tool versus alternatives like search_notes or read_note, nor does it mention prerequisites (e.g., Apple Notes app requirements) or when not to use it.

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/lanchuske/local-mcp-releases'

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