notes-mcp

by gabed5303-ops

Overview Schema Source Related Servers Discussions Admin

Python

Local

add_note

Create a new note with a title, body, and optional tags. Returns the note with its assigned ID for later reference.

Instructions

Create a new note with a title, body, and optional tags.

Returns the stored note, including its assigned ID — reference that ID in later get/update/delete calls.

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

Input Schema

Name	Required	Description
`body`	Yes	Body text of the note (plain text or Markdown).
`tags`	No	Optional tags to categorize the note, e.g. ['ideas', 'physics'].
`title`	Yes	Title for the new note.

Output Schema

Name	Required	Description
`id`	Yes	Unique numeric ID of the note.
`body`	Yes	Full body text of the note.
`tags`	Yes	Tags attached to the note.
`title`	Yes	Title of the note.
`created_at`	Yes	Creation time (ISO 8601, UTC).
`updated_at`	Yes	Last modification time (ISO 8601, UTC).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations correctly indicate non-read-only and non-destructive behavior. The description adds value by explaining the return behavior (stored note with assigned ID), which aids the agent.

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?

The description is two sentences, front-loaded with the core action, and contains no unnecessary words. Every sentence provides essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and comprehensive parameter descriptions, the description is complete. It explains the purpose, return value, and hint for future usage, fulfilling all requirements for a creation tool.

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 already describes all parameters clearly. The description adds no additional semantic meaning for parameters beyond what the schema provides, so baseline 3 is appropriate.

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 clearly states 'Create a new note with a title, body, and optional tags.' It uses a specific verb ('Create') and resource ('note'), and distinguishes itself from sibling tools like delete, update, and list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description advises referencing the returned ID for later get/update/delete calls, setting clear usage context. It implies when to use the tool (to create a note) but does not explicitly mention when to avoid it.

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

Deploy Server