Skip to main content
Glama
Wolfe-Jam

mcp-context-card

by Wolfe-Jam
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

remember

Persist facts across sessions by writing them to a file with a stable ID. Reuse an ID to update a fact in place, or create a new entry for a new ID, so you can recall it later.

Instructions

Persist a fact past the session boundary — written to a .fafm file, not held in memory. Reusing an existing id replaces that fact's text in place (no duplicate); a new id appends. Facts are written verification_status: unverified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesA stable key you choose for this fact — pass the same id later to recall or forget it. Exact match, case-sensitive, any string; keep it short and meaningful (e.g. "deploy-target", "db-url"). Reusing an id updates that fact rather than adding a second one.
textYesThe fact itself, as plain prose. Stored verbatim and returned as-is by recall.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.2
    • addedInput schema / properties / id / description
      Added value: +"A stable key you choose for this fact — pass the same id later to recall or forget it. Exact match, case-sensitive, any string; keep it short and meaningful (e.g. \"deploy-target\", \"db-url\"). Reusing an id updates that fact rather than adding a second one."
    • addedInput schema / properties / text / description
      Added value: +"The fact itself, as plain prose. Stored verbatim and returned as-is by recall."
  2. First observedv0.5.1

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that facts go to a .fafm file rather than memory, that reusing an id replaces text in place, and that new ids append. It also exposes the written verification_status. It does not describe return or failure behavior, but the core side effects are clearly stated.

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?

Two tight sentences with the core purpose front-loaded. Every clause adds a distinct behavioral fact, and there is no filler or repetition.

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-parameter write tool with no output schema, the description covers persistence location, update/replace semantics, append behavior, and written status. The main gaps are the lack of a return-value/confirmation description and explicit failure modes, but these are minor at this complexity.

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%, and both id and text are already well-documented in the schema. The description mostly restates the id replacement semantics found in the schema, adding little parameter-level meaning beyond it.

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?

States the exact operation: persistently storing a fact past the session boundary, with explicit update-vs-append semantics. This clearly distinguishes it from read-oriented siblings like recall and read_agents_md.

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: any fact that must survive the session or be updated by id. It does not explicitly contrast with recall/forget or state when not to use it, but the durable-write context is unambiguous.

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

Install Server

Other Tools