Skip to main content
Glama

Remember a note

remember

Save one short learner fact, like an exam that is over or a study preference, so later agents can see where the learner left off across folders.

Instructions

Save a short note about the learner. Every agent that connects to godspeed later sees it under "Where you left off", in any folder. Save what the learner tells you outside lessons that will matter next time: an exam that is over, what they plan to study next, how they like to learn. One fact per note, at most 200 characters. Never save passwords or private details. The learner can see and delete notes in Settings → Connection.

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": {
      "text": "<text>"
    },
    "name": "remember"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe note, one line.
space_idNoThe space the note is about, if one (from list_spaces).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the persistence model (every agent connecting later sees it under "Where you left off", across any folder), the human-visibility and deletability of the note via Settings → Connection, and a privacy prohibition. That is exactly the kind of consequence-of-writing context the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false) cannot convey.

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 core action is front-loaded in the first sentence and the remaining sentences are each doing work (content guidance, limits, privacy, visibility). The 200-character restatement duplicates the schema's maxLength and is the only sentence not fully earning its place.

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 two-parameter write tool with no output schema, the definition covers what to write, how much, what to avoid, where it surfaces later, and how the learner can remove it. An agent has everything needed to call it correctly and responsibly.

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?

Schema description coverage is 100%, so both text and space_id are already documented, which sets the baseline at 3. The description reinforces the 200-character limit and the one-fact-per-note convention for text, but adds nothing about space_id beyond the vague phrase "in any folder".

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?

"Save a short note about the learner" is a specific verb plus resource, and the follow-up sentence enumerates exactly what content belongs in a note (finished exams, next study plans, learning preferences). It does not differentiate against nearby siblings such as save_rule or import_notes, so an agent must infer that boundary, but the tool's own scope is unambiguous.

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?

The description gives a clear trigger condition ("what the learner tells you outside lessons that will matter next time") and an implicit exclusion (facts arising inside lessons belong elsewhere). It also sets hard constraints (one fact per note, ≤200 characters, never passwords or private details). It stops short of naming an alternative tool for cases this one doesn't cover.

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