Skip to main content
Glama

SourceGeek

Remember a fact

remember
Destructive

Remember one stable fact or preference — for the current user, or (shared: true) for the whole workspace. Saving under an existing key replaces its value.

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
keyYes
valueYes
sharedNoSave into the workspace-shared bucket every member sees. Only when the user explicitly asked for a team-wide rule.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, and the description earns credit for explaining why: "Saving under an existing key replaces its value," which tells the agent exactly what prior data is lost. It also discloses the two-bucket scoping model (per-user vs. workspace-shared), which the annotations do not. It stops short of stating whether the call confirms success or returns the stored value, and there is no guidance on undoing an overwrite.

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 short sentences, front-loaded with the core action and scope, then the overwrite caveat. Every clause carries information an agent needs; nothing is redundant with the title or annotations.

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 three-parameter write tool with no output schema, the definition covers scope, overwrite semantics, and the team-wide guardrail. The remaining omissions — what the call returns, and how a memory is later read or deleted — are minor but real for a destructive operation.

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 only 33% — only `shared` is documented in-schema, while `key` and `value` carry just pattern/length constraints. The description partially compensates by implying `key` is an upsert identifier ("Saving under an existing key replaces its value"), but it never explains key naming conventions or that `value` holds the fact text, leaving the two required parameters under-specified.

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?

"Remember one stable fact or preference" gives a specific verb and a tightly scoped resource, and the parenthetical "(shared: true) for the whole workspace" clarifies the two storage scopes. The only gap is that it does not contrast itself with any sibling, though the listed siblings are unrelated lookup tools, so an agent can still identify this as the write path for persisting facts.

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

Usage Guidelines3/5

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

The word "stable" implicitly steers the agent away from transient data, and the schema's `shared` description explicitly restricts workspace writes to cases where "the user explicitly asked for a team-wide rule." However, the description itself offers no explicit when-to-use/when-not-to-use framing or any mention of how to retrieve or remove a stored fact later.

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