Skip to main content
Glama
furui

furui

Remember

remember

Store facts, preferences, decisions, or lessons as long-term memories with tags, importance, and optional pinning so AI agents can recall and reinforce them.

Instructions

Store a new long-term memory.

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
tagsNoOptional short keywords; they also count toward recall matching.
textYesThe fact, preference, decision or lesson to remember.
pinnedNoIf true, the memory never decays below a floor and is never pruned.
importanceNo1 (trivia) to 5 (critical). Scales the memory's score.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden, yet it discloses almost nothing: no deduplication or conflict behavior, no scope (user vs. global), no permission requirements, no statement that this creates durable state. Only the phrase "long-term" hints at persistence, and the decay/pruning semantics live solely in the parameter schema.

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

Conciseness3/5

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

The single sentence is front-loaded and contains no filler, but it is arguably under-sized for a four-parameter mutation tool in a five-tool memory family. Brevity here costs information rather than earning it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 not be explained, but for a memory-creation tool with no annotations the description should still say whether duplicates are merged, what scope the memory lands in, and how it interacts with recall and prune. None of that is present.

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 text, tags, pinned and importance are all documented in the schema itself, including the decay floor and importance scale. The description adds no additional meaning beyond that, which is the expected baseline when the schema does the work.

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?

The description gives a specific verb ("Store") and resource ("a new long-term memory"), which is clearly distinct from the sibling operations forget, prune, recall and stats. It stops short of explicitly naming a sibling to contrast with, so an agent must infer the boundary itself.

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

Usage Guidelines2/5

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

There is no when-to-use guidance beyond the implicit fact that this is the write side of memory management. Nothing says when to prefer remember over recall, what happens if a similar memory already exists, or whether new memories should be pinned or tagged in particular situations.

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

Deploy Server

Other Tools