Skip to main content
Glama

CarlNotes

Save a tasting note

save_note
Destructive

Create a tasting note on a CarlNotes topic or team page, or change one you may edit. With no note_id, it creates a note from a name and a visibility the page allows. With a note_id, it saves a new name, a new visibility, which only the note's author changes, or a new html body, which needs the version read_notes returned. A body save replaces the whole note and keeps no history, and a stale version saves nothing. Use it when the user asks Carl or CarlNotes to write a note, add a tasting note, or edit my note.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNoThe note's whole new body as html.
nameNo
note_idNoThe note to change. Leave it out to create a note.
team_idNoA team whose page holds the notes, in place of topic_id.
versionNoThe version read_notes returned, which a body save needs.
topic_idNoThe topic's id. Optional on a topic-bound server, which already knows its topic.
visibilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructive and non-idempotent behavior, and the description adds that a body save replaces the entire note with no history and that a stale version saves nothing. It also discloses that only the note's author can change visibility, adding meaningful permission context beyond the annotations.

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

Conciseness4/5

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

The description is front-loaded with purpose and the key create/update rules, followed by terse caveats and user triggers. A few sentences are dense, but no content feels wasted or irrelevant.

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 7-parameter mutation tool with no output schema, the description covers the critical create/update path, destructive replacement, versioning, and visibility permissions. It relies on the schema for team_id/topic_id selection and field constraints, which is acceptable.

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

Parameters4/5

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

With 71% schema coverage, the description adds conditional meaning: omitting note_id creates, providing note_id updates, version is required for html body saves, and visibility changes are author-only. It leaves team_id versus topic_id selection and name length constraints to the schema, which documents them.

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 states specific verbs (create/change) and the resource (tasting note) on a CarlNotes topic or team page, and clearly distinguishes creation from update via note_id. It also differentiates from read_notes by requiring the version that read_notes returned for body saves.

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?

It gives explicit user-trigger phrasing: 'write a note, add a tasting note, or edit my note,' and notes the read_notes dependency for version. It does not say when not to use this tool or name alternatives like delete_note, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.