Skip to main content
Glama
Sign In
notes-mcp

notes-mcp

by pdegner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_note

Save a new note as Markdown by providing a title, content, and optional tags for grouping.

Instructions

Save a new note.

Args:
    title: Short title for the note.
    content: The body of the note, as Markdown.
    tags: Optional labels for grouping, e.g. ["work", "ideas"].

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
tagsNo
titleYes
contentYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior2/5

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

Since no annotations are provided, the description must disclose behavioral traits. It only says 'Save a new note' and explains parameters, without mentioning return behavior, idempotency, or side effects like persistence or interaction with other tools. This is a significant gap for a create operation.

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 concise and front-loaded with the action 'Save a new note.', followed by clear, minimal parameter documentation. There is no fluff or redundant 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?

For a simple create operation, the description covers all necessary invocation details: required parameters, optional tags, and content format. An output schema exists, so the absence of return-value descriptions is acceptable. The tool is fully invocable based on this description.

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

Parameters5/5

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

The schema has no descriptions (0% coverage), but the description compensates by explaining each parameter: title is a short title, content is the body in Markdown, and tags are optional labels with an example array. This meets the need for parameter meaning.

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 uses a specific verb 'Save' and clearly identifies the resource as 'a new note'. This distinguishes it from sibling tools like list_notes, get_note, and delete_note, which operate on existing notes.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description only states the action and lists parameters, so usage is implied rather than clearly contextualized. It does not mention any exclusions or direct the user to other tools for different needs.

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

Deploy Server

Other Tools