Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

create_note

Create a Markdown note with a title, optional tags, reminders, pinning, and background styling. Add formatted content such as headings, lists, links, and code blocks.

Instructions

Create a note. Put the title in title, not as a heading in content.

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
titleYes
tagIdsNoTag ids from list_tags
contentNoMarkdown. Supported: # headings (1-3), **bold**, *italic*, <u>underline</u>, ~~strike~~, ==highlight==, [links](url), - bullets, 1. numbered, - [ ] / - [x] checklists (nest with 4 spaces), > quotes, ``` code blocks.
isPinnedNo
reminderNoReminder; null removes it
backgroundNoNote background; null clears it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already establish a non-destructive, non-open-world write (readOnlyHint=false, destructiveHint=false), so the safety profile is covered. The description adds nothing further: no statement about what is returned (e.g., a new note id), whether duplicates are allowed, or any permission constraints, which matters because there is no output schema.

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?

Two short sentences, front-loaded with the action and followed by the one high-value caveat. Nothing is redundant or padded.

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 six-parameter creation tool the description covers the riskiest pitfall but omits the outcome — no indication of what the call returns (note id?) despite the absence of an output schema, which an agent would need to chain into append_to_note or share_note. Adequate but with a clear gap.

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 67%, and the description adds real meaning by resolving an ambiguity the schema leaves open: the title must go in the `title` field rather than as a markdown heading inside `content`, whose schema explicitly supports `#` headings. This prevents a plausible misuse that the schema alone would not forestall; the remaining params (tagIds, reminder, background) are already well documented in the schema.

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 opens with a specific verb+resource ("Create a note"), so the agent knows exactly what operation is performed. It does not distinguish this from siblings like append_to_note or update_note, but the core action is unambiguous.

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 guidance and no mention of alternatives such as append_to_note (for adding to an existing note) or update_note. The only guidance is about field placement, which is parameter-level rather than tool-selection-level.

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