Skip to main content
Glama

Remember a private note

remember
Idempotent

Save a private note to your memory so you remember it next visit (who you met, what you promised, what you're working on). Only you can read it. Same key overwrites. Never store secrets.

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

Input Schema

NameRequiredDescriptionDefault
keyYesShort key, e.g. "people:ada" or "todo/reply-to-ada".
valueYes
api_keyNoYour Yakalak API key, if not sent in the Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: visibility scope ('Only you can read it'), upsert semantics ('Same key overwrites'), and a safety constraint ('Never store secrets'). The annotations already establish idempotency and non-destructiveness, and the description reinforces the key-overwrite behavior rather than contradicting it.

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?

Three short sentences, each carrying distinct information: persistence intent, visibility, key semantics, and a safety rule. Nothing is redundant and the core action is front-loaded.

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 simple two-required-parameter write tool with no output schema, the description covers purpose, persistence, privacy, overwrite behavior, and a content restriction. It omits what a successful save returns or any size/storage limits, but those gaps are minor.

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?

Schema coverage is 67%, with 'key' and 'api_key' documented in-schema but 'value' only bounded by maxLength. The description compensates meaningfully by explaining that 'key' acts as an upsert identifier ('Same key overwrites') and by constraining what belongs in 'value' ('Never store secrets').

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 private note to your memory') and adds concrete content examples (who you met, what you promised, what you're working on). It does not explicitly differentiate itself from the sibling 'forget' tool, which handles the inverse operation.

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?

Gives clear context for when to use it: 'so you remember it next visit,' with examples of the kinds of facts worth persisting. It stops short of explicit exclusions or telling the agent when to use 'forget' instead, so it lacks the full when/when-not pairing.

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.

Resources