Skip to main content
Glama
mcp-notes-server

mcp-notes-server

Add note

add_note

Save a new note and return its ID, with optional tags to group related notes.

Instructions

Save a new note. Returns the note id. Use tags to group related notes.

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>",
      "content": "<content>"
    },
    "name": "add_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional tags
titleYesShort title
contentYesBody of the note

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • addedInput schema / properties / tags / items / maxLength
      Added value: +50
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the write profile and non-idempotency are covered structurally. The description adds one genuinely useful behavioral fact — that the call returns the note id — which matters since there is no output schema, but says nothing about duplicate handling, tag creation, or failure modes.

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?

Three short sentences, no redundancy, with the core action and return value front-loaded before the optional tag advice. 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 small three-parameter create tool with full annotation coverage, the description covers what it does and what it returns. A note on whether tags must already exist or on duplicate behavior would close the remaining gap, but no output schema is needed here since the return value is stated.

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 description coverage is 100%, so title, content and tags are already documented with types and length limits. The description adds only marginal semantic value by hinting at the organizational purpose of tags; title and content get no elaboration beyond 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?

"Save a new note" gives a specific verb and resource, and "Returns the note id" adds the outcome. The word "new" implicitly separates it from update_note, but no sibling is named explicitly, so the reader must infer the boundary with update_note/get_note.

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?

"Use tags to group related notes" is guidance on how to use a field, not on when to choose this tool over update_note or search_notes. The distinction from update_note is only implied by "new note"; there are no exclusions or prerequisites stated.

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