Skip to main content
Glama

Record Memory Feedback

feedback

Rate whether a recalled memory was useful to tune its salience score, so outdated or noisy entries lose priority and helpful memories surface first.

Instructions

Record whether a recalled memory was useful and adjust its salience score.

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": {
      "id": "<id>",
      "useful": "<useful>"
    },
    "name": "feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMemory ID to rate.
usefulYesTrue if helpful, false if noisy or outdated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and non-destructive, so the safety profile is covered; the description adds the non-obvious effect that a salience score is mutated. It does not say whether repeated calls compound the adjustment (relevant since idempotentHint=false) or how large/reversible the change is, which keeps it below 5.

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

Conciseness4/5

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

A single efficient sentence with no filler, and the primary action is front-loaded before the side effect. Nothing is redundant, though there is no structural separation of purpose from consequence.

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 two-parameter mutation tool with full schema coverage, annotations, and no output schema, the definition covers both what is recorded and what changes. The remaining gap is the persistence semantics of the salience adjustment across repeated feedback calls, which an agent would need to reason about.

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%, with both `id` and `useful` documented inline, so the baseline is 3. The description adds no syntax, format, or validation detail beyond what the schema already states.

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?

"Record whether a recalled memory was useful" names a specific verb and resource, and adds the consequence ("adjust its salience score"), which separates it from siblings like recall_memories or encode_memory. It stops short of explicitly naming a sibling or stating the boundary, but the operation is unambiguous.

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 phrase "a recalled memory" suggests calling this after recall_memories, but there is no explicit when-to-use statement, no precondition (e.g. that the ID must come from a prior recall), and no mention of alternatives such as forget_memory for outdated entries despite "outdated" appearing only in the schema.

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