Skip to main content
Glama

Remember preference

remember

Save or update a user preference by category and key; re-saving the same key increases confidence and returns a row ID for later removal.

Instructions

Save or update a user preference (category+key upsert). Re-saving the same key increases confidence by 0.1 (cap 1.0). Returns the row id for forget().

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

Input Schema

NameRequiredDescriptionDefault
keyYesShort stable key, e.g. package_manager
valueYesThe preference value
categoryYesPreference category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.2.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses upsert semantics, the confidence bump of +0.1 per re-save capped at 1.0, and the return value (row id). It does not say what happens to the previous value on a same-key write, which is the main remaining gap for a mutation tool.

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 (upsert identity, confidence behavior, return value), with the core action front-loaded. No filler or restatement of the tool name.

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 3-parameter, non-nested, annotation-free write tool with no output schema, the description covers identity semantics, side effects, and the return value. Only the overwrite/conflict behavior and any failure conditions are left unstated.

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 100%, so the baseline is 3, but the description adds genuine meaning the schema cannot express: the pair category+key is the upsert identity, so agents know re-saving with the same pair mutates rather than duplicates. That is the single most decision-relevant fact about these parameters.

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?

Description names a specific verb (save/update) and resource (a user preference) and adds the key mechanic, a composite category+key upsert. It implicitly separates itself from siblings like save_lesson and update_memory via the term 'user preference', but never names or contrasts those siblings explicitly.

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?

Usage is only implied: the mention of returning a row id 'for forget()' hints at the store-then-remove lifecycle, but nothing states when to call remember versus save_lesson, update_memory, or link_memory. An agent must infer the routing from the name alone.

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