Skip to main content
Glama

Remove Memory Relationship

remove_memory_relationship

Remove one explicit link between personal memories; both memories are kept and only the link is marked removed.

Read the link with memory_relationships first and pass its relationship_id and version. A stale expected_version returns Conflict; repeating the same removal returns the removed link instead of an error.

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": {
      "memory_id": "<memory_id>",
      "relationship_id": "<relationship_id>",
      "expected_version": "<expected_version>"
    },
    "name": "remove_memory_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_idYesmemory_id (UUID) of either memory the link joins.
relationship_idYesrelationship_id of the link, from memory_relationships.
expected_versionYesThe link's version from memory_relationships; a stale value returns Conflict.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / expected_version / description
      Previous value: -"Optimistic-concurrency version read from the current record; a stale value is rejected with VERSION_CONFLICT."New value: +"The link's version from memory_relationships; a stale value returns Conflict."
    • removedInput schema / properties / expected_version / title
      Removed value: -"Expected Version"
    • changedInput schema / properties / memory_id / description
      Previous value: -"Exact XMemo memory reference shown by search or recall."New value: +"memory_id (UUID) of either memory the link joins."
    • removedInput schema / properties / memory_id / title
      Removed value: -"Memory Id"
    • changedInput schema / properties / relationship_id / description
      Previous value: -"Input value for the Remove Memory Relationship tool."New value: +"relationship_id of the link, from memory_relationships."
    • removedInput schema / properties / relationship_id / title
      Removed value: -"Relationship Id"
    • removedInput schema / title
      Removed value: -"remove_memory_relationshipArguments"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the crucial behavioral trait that this is a non-destructive soft removal (memories survive), that a stale expected_version yields Conflict, and that a repeated removal returns the already-removed link rather than erroring. That last clause is arguably in tension with idempotentHint=false, but it is a return-value detail rather than a side-effect contradiction, and the description supplies information the annotations omit.

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 tight sentences with no filler: the first establishes what is and is not destroyed, the second establishes the prerequisite and the two edge-case outcomes. Front-loaded and appropriately sized for a three-parameter mutation.

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?

With no output schema, the description carries return-value burden and does explain the conflict and repeat-call outcomes, but it does not describe the shape of a successful response or whether the removal can be undone. For a simple three-parameter tool this is close to complete, with only minor gaps.

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; the description earns above that by tying relationship_id and expected_version to their source tool (memory_relationships) and explaining the Conflict consequence of a stale version. It adds workflow meaning the schema alone does not convey.

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 names a specific verb and resource (remove one explicit link between memories) and immediately disambiguates scope: both memories are kept and only the link is marked removed. That distinction separates it from hard-delete or memory-level siblings without the agent needing to open any 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?

It gives an explicit prerequisite workflow: read the link with memory_relationships first, then pass that relationship_id and version. That is clear when-to-use guidance with a named sibling. It stops short of stating when not to use it (e.g., when the relationship should be restored rather than removed) or what happens if the link no longer exists.

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.