Skip to main content
Glama

Add note

add_note

Save a new note with a title, Markdown body, and optional tags to a SQLite-backed personal knowledge base for later search and reuse.

Instructions

Save a new note.

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

Input Schema

NameRequiredDescriptionDefault
bodyNoMarkdown text
tagsNo
titleYes

Output Schema

NameRequiredDescriptionDefault
idYes
uriYesResource URI for this note
urlNoSet for bookmarks
bodyYes
tagsYes
titleYes
created_atYes
updated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond them — notably it never warns that the call is non-idempotent, so re-saving the same note creates duplicates rather than updating, nor whether tags are auto-created.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single short sentence is front-loaded and free of waste, but it is under-specified rather than concise: four words for a tool with three parameters and creation semantics that materially affect how it should be called.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. However, for a non-idempotent create tool with a required title and a large free-text body, the description leaves gaps an agent needs: duplicate-title behavior, tag creation side effects, and required fields.

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

Parameters2/5

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

Schema description coverage is only 33%: title (required) and body are essentially undocumented, with only tags carrying a meaningful schema description. The description compensates for none of this — it does not mention the required title, the 200-character title limit, or the 50,000-character Markdown body.

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 ("Save a new note"), and the word "new" scopes it to creation, implicitly separating it from update_note and delete_note. It does not explicitly name or contrast with any sibling, so it stops short of a 5.

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, no prerequisite or permission context, and no mention of alternatives such as update_note when the note already exists. The agent must infer the routing decision entirely.

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