Skip to main content
Glama

Note Management

manage_note
Destructive

Store, retrieve, and delete novel-scoped scratch notes with badge-based access control for game masters, players, or shared use, plus GM-only server notes for campaign rules or session reminders.

Instructions

Manage Novel-scoped scratch notes, badge-scoped to game_master (default), player, or shared. set replaces the note content; badge_scope defaults to game_master and controls which badge can read it; remove deletes one note, and the Player badge cannot remove a game_master note; list hides game_master notes from non-GM badges. set_server stores a GM-only server-level note with an optional narrative_tag; remove_server deletes it; list_server returns summaries unless detail is set. Mutating note actions persist and are audited, but are not undoable. Use when: storing scratch state the caller will reuse. Do NOT use when: recording durable world facts — use manage_lore (action: set); handling external documents — use manage_corpus; ranking derived text — use manage_knowledge.

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": {
      "action": "<action>"
    },
    "name": "manage_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoThe note key (set/remove/set_server/remove_server).
actionYesset, remove, list, set_server, remove_server, or list_server.
detailNoReturn full server notes instead of summary entries (list_server).
contentNoThe note content (set/set_server).
badge_scopeNogame_master, player, or shared (set).
narrative_tagNoOptional narrative tag (set_server).

Output Schema

NameRequiredDescriptionDefault
textNoHuman-readable text envelope mirroring the structured result (REQ-001, REQ-548a).
statusYesMachine-readable result status: OK, NEED_INPUT, WARNING, PARTIAL, or an error category (REQ-002, REQ-548c).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.10.13
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Return full server notes instead of summary entries (list_server).",
      +  "type": "boolean"
      +}
  2. Addedv1.0.3

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description reinforces that mutating actions 'persist and are audited, but are not undoable'. It further discloses permission behavior ('the Player badge cannot remove a game_master note', 'list hides game_master notes from non-GM badges') and GM-only server-note scope, which annotations cannot convey. It stops short of describing the audit trail or any rate/size limits on note content.

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?

Front-loaded with the core purpose, then per-action clauses, then a crisp Use/Do-NOT-use block; every sentence carries information. The first sentence is a dense run-on stacking five action behaviors, which slightly hurts scanability.

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?

An output schema exists so return values need no explanation, and the description covers what matters for a 6-param, 6-action mutation tool: per-action semantics, scope defaults, cross-badge permission rules, and irreversibility. Nothing an agent needs to invoke it correctly is missing.

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 100% schema coverage the baseline is 3, but the description adds meaning the schema lacks: badge_scope defaults to game_master and 'controls which badge can read it', and detail on list_server returns 'summaries unless detail is set'. It does not explain narrative_tag's purpose beyond the schema's 'Optional narrative tag'.

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?

Opens with a specific verb and resource plus its scope: 'Manage Novel-scoped scratch notes', then enumerates every action (set/remove/list/set_server/remove_server/list_server) with what each does. An agent can distinguish it from manage_lore, manage_corpus, and manage_knowledge purely from this text.

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

Usage Guidelines5/5

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

Contains explicit 'Use when' and 'Do NOT use when' blocks that name three alternative siblings (manage_lore action: set, manage_corpus, manage_knowledge) with the condition selecting each. Nothing about routing is left to inference.

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