Skip to main content
Glama

Notes: create note

notes_create_note
Destructive

Creates a new Apple Notes note from supplied text, with the first line used as the title, so agents can capture notes programmatically.

Instructions

Create a new note in Apple Notes with the given text. (risk: mutating)

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": {
      "body": "<body>"
    },
    "name": "notes_create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe note's content. The first line becomes its title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so '(risk: mutating)' merely restates the structured safety profile in softer wording. The description adds nothing about which account/folder the note lands in, permission prompts, or failure behavior for what is flagged as a destructive-capable operation.

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?

One front-loaded sentence that names the action and target immediately. The trailing risk parenthetical is redundant with annotations but costs little.

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 single-parameter creation tool with no output schema, the description is barely adequate. It never indicates whether the new note's identifier or location is returned, which matters because an agent likely needs it to follow up with notes_read_open_note.

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

Parameters3/5

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

Schema coverage is 100% and the body parameter is fully documented, including the meaningful detail that the first line becomes the title. The description's 'with the given text' adds no syntax, length, or formatting detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource with target application: 'Create a new note in Apple Notes.' This distinguishes it sufficiently from the listed siblings, which all operate on other apps (TextEdit, code, Slack), though no explicit sibling routing is given.

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 guidance on when to use this versus notes_read_open_note or the TextEdit write tools, no prerequisites (e.g. automation permissions), and no exclusions. The agent must infer usage entirely from the name.

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