Skip to main content
Glama

Remember a style preference

remember

Saves one lasting preference of this member (e.g. "captions always bigger", "never black and white") so every future edit applies it. One short line. Not for one-off notes about a single video.

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

Input Schema

NameRequiredDescriptionDefault
noteYesThe preference in one short line, in plain words
slugNoThe editor it came from, if any
sourceNoimport = copied from ~/.cuttr/BRAND.md

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the saved preference is lasting and will apply to every future edit, but it does not explain duplicate handling, overwrite behavior, permissions, or what confirmation the agent should expect after saving.

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?

The description is front-loaded with the core action and scope, then immediately gives examples and the key exclusion. Every sentence serves a purpose, and the short-line constraint is stated efficiently.

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 save-a-preference tool with no output schema and full schema coverage, the description gives enough context to call it correctly. The main remaining gap is what happens after saving, such as confirmation or duplicate handling, but the core scope and exclusions are complete.

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 the schema already documents all three parameters. The description reinforces that the preference should be one short line, but it adds little semantic detail for slug or source beyond what the schema already provides. Baseline 3 is appropriate.

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?

The description uses a specific verb and resource: saves a lasting preference for this member, with concrete examples such as captions always bigger. It also distinguishes the tool from one-off notes about a single video, so an agent can identify the intended action without opening the schema.

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?

The description clearly states when to use it: for a lasting preference that should apply to every future edit. It also states when not to use it: not for one-off notes about a single video. It does not name sibling alternatives such as forget or log_video, which keeps it from a full 5.

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