Skip to main content
Glama

create_note

Create a note from plain text, using the title as its first heading and default folder unless another folder is specified.

Instructions

Create a note from plain text. The title becomes the first line (a heading). Notes uses the default folder when 'folder' is not given.

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": {
      "title": "<title>"
    },
    "name": "create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoPlain text body. Line breaks are kept.
titleYesTitle of the note, on one line.
folderNoFolder name (any case) or id.
accountNoAccount name, for example iCloud. Ignores case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world write, and the description adds genuinely new behavior: the title is rendered as the first line/heading, and the note lands in the default folder when 'folder' is absent. It does not cover what happens on duplicate titles or what identifier is returned, which keeps it out of the top band.

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?

Three compact sentences with the core purpose front-loaded and no filler. The minor grammatical slip ("Notes uses the default folder") is the only blemish; every sentence carries information.

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?

For a four-parameter create tool with full schema descriptions and useful annotations, this covers purpose, formatting, and default targeting well. With no output schema, return values need not be described, so the remaining gap is small.

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%, so the baseline is 3, but the description adds meaning beyond the schema for 'title' by explaining it becomes the first line as a heading, and for 'folder' by stating the default-folder fallback. 'body' and 'account' semantics remain entirely schema-supplied.

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 ("Create a note from plain text") plus a formatting rule (the title becomes the first line as a heading). It is immediately clear what the tool produces, though it never explicitly distinguishes itself from siblings like append_to_note or update_note.

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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named or implicitly ruled out. The only contextual statement (default folder when 'folder' is omitted) is a behavior, not a usage rule, so an agent must infer on its own that this is for new notes rather than appending to existing ones.

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