Skip to main content
Glama

memory_resolve

Destructive

Resolve conflicting memories by selecting a correct winner using content hashes, ensuring accurate persistent storage and retrieval.

Instructions

Resolve a memory conflict by choosing a winner

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": {
      "winner_hash": "<winner_hash>",
      "loser_hash": "<loser_hash>"
    },
    "name": "memory_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
loser_hashYesContent hash of the incorrect memory
winner_hashYesContent hash of the correct memory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

The destructiveHint=true annotation already signals a mutating, potentially irreversible operation, so the description's bar is lower, but it still adds almost nothing: it does not say whether the loser is deleted, archived, or merely marked superseded, nor whether the action is reversible or requires confirmation. 'Choosing a winner' leaves the fate of loser_hash entirely unspecified.

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 short sentence with zero filler and the core action front-loaded. It is efficient rather than padded, though the brevity comes at the cost of the missing behavioral detail scored elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive two-hash mutation with no output schema, an agent needs to know the post-condition (what happens to the losing memory) and how to discover a conflict pair in the first place. Neither is present, so the definition is not complete enough to invoke this confidently in a multi-step workflow.

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 coverage is 100%, with both winner_hash and loser_hash documented as content hashes, so the schema carries the parameter burden. The description's wording 'winner'/'loser' loosely aligns with those fields but adds no format, sourcing, or error semantics beyond them — baseline 3.

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?

States a specific verb ('resolve') and resource ('memory conflict') plus the mechanism ('choosing a winner'), which is far more than a restatement of the name. It stops short of distinguishing itself from likely-adjacent siblings such as memory_conflicts (detection) or memory_consolidate (merging), so an agent must still guess when this is the right call.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus memory_conflicts, memory_consolidate, memory_update, or memory_delete — all plausible ways to handle a contradictory pair. The description never states a precondition (e.g. 'use after memory_conflicts surfaces a pair') or an exclusion.

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