Skip to main content
Glama

create_note

Create a note in Apple Notes to capture information. Use this tool to add notes without manual input.

Instructions

Create a new note in Apple Notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:34-34 (registration)
    The tool 'create_note' is registered as part of a static TOOLS array with description 'Create a new note in Apple Notes'.
    ["create_note", "Create a new note in Apple Notes"],
  • The handler for 'create_note' (and all other tools) is a generic stub that returns 'This is an inspection stub...' since the real server is a native binary. The handler is defined inline in the for loop at lines 106-109.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
Behavior2/5

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

No annotations are provided, so the description carries full burden for disclosing behavioral traits. It only states the action without detailing side effects, requirements, or outcomes (e.g., what happens after creation, whether authentication is needed). This minimal disclosure is insufficient for an agent to fully understand the tool's behavior.

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 a single sentence that is concise and to the point. It could be improved with additional details about the tool's behavior, but it is appropriately sized and front-loaded with the key action.

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?

For a simple parameterless creation tool, the description covers the basic function. However, it lacks additional context such as whether the tool creates a blank note, any prerequisites, or the expected behavior in edge cases. It is adequate but leaves gaps in completeness.

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?

The input schema has zero parameters, and schema description coverage is 100% trivially. The description adds no extra parameter meaning because there are none, but it does not clarify the behavior of the tool when invoked without input. However, the schema is self-sufficient, earning a baseline of 4.

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 'Create a new note in Apple Notes' uses a specific verb 'Create' and clearly identifies the resource 'a new note in Apple Notes'. It effectively distinguishes itself from sibling tools like list_notes, read_note, and search_notes, which are read or list operations.

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?

While the purpose of creating a note is clear, the description provides no guidance on when to use this tool versus alternatives. It does not mention any preconditions or scenarios where this tool is appropriate, leaving the agent to infer usage from context alone.

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