Skip to main content
Glama

note_save

Save or update project-scoped working notes—decisions, gotchas, specs, or general notes—so context persists across conversations and tasks.

Instructions

Save or update a project-scoped working note (decision, gotcha, spec, or note) persisted across conversations for this project.

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_markdown": "<body_markdown>"
    },
    "name": "note_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
titleYes
pinnedNoPin important invariants into turn briefs.
note_idNoExisting note ID to update.
task_idNoOptional task ID to scope the note to.
project_idNoOptional project ID (auto-resolved when omitted).
body_markdownYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add useful behavior beyond structured data: the note persists across conversations, is project-scoped, and has four semantic kinds. It omits the important upsert semantics — whether supplying note_id replaces the entire body, whether a same-title save creates a duplicate, and whether updates are destructive or reversible.

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?

A single dense sentence, front-loaded with the verb and resource, with the persistence/scope qualifier and kind enumeration each adding distinct information. No filler or repetition.

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?

Given 7 parameters, no annotations, and no output schema, the description covers what a note is and where it lives but not how the create/update branch behaves or what comes back. Adequate to identify the tool, thin for invoking it confidently on the update path.

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?

At 57% schema coverage across 7 params, the description contributes by clarifying that the enum values are note categories and that the note is project-scoped, which frames project_id. It adds nothing for pinned, task_id, note_id (the create-vs-update switch), title, or body_markdown, leaving the coverage gap partly unfilled.

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 pair (save or update) and a specific resource (project-scoped working note), and enumerates the supported kinds. It does not name or differentiate itself from close siblings such as memory_save, ui_save_note, or note_list, so an agent still has to infer which save-tool to pick.

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?

"Persisted across conversations for this project" implies the use case (durable, project-scoped knowledge rather than session chatter), which is real implied guidance. However, it never states when not to use it or how it relates to memory_save / ui_save_note, and gives no prerequisites or exclusions.

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