Skip to main content
Glama

memory_quarantine_release

Release a quarantined memory back into active use when it is valid, such as when the contradicted belief was wrong. Restores memories held during conflict review.

Instructions

Release a memory from quarantine. Use when a quarantined memory is valid (e.g., the contradicted belief was wrong).

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": {
      "content_hash": "<content_hash>"
    },
    "name": "memory_quarantine_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_hashYesContent hash of the quarantined memory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv13.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, so the agent knows this is a mutation. The description clarifies the semantic condition for release but does not say what happens to the memory afterward (does it return to the active store?), whether the release is reversible, or what permissions are needed. Useful context, but a meaningful 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?

Two short sentences: the action first, then the condition for use. No redundant or filler wording.

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 single-parameter mutation with no output schema and minimal annotation coverage, the description covers what it does and when to invoke it. It could add one clause about the post-release state of the memory, which is the main missing piece.

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?

There is a single required parameter, content_hash, with 100% schema description coverage, so the schema already carries the parameter semantics. The description adds nothing about the hash format or where to obtain it, so baseline 3 applies.

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 and resource ('Release a memory from quarantine'), which unambiguously describes the action and pairs naturally against the sibling memory_quarantine_list. It does not explicitly name a sibling to differentiate from, keeping it short of a 5.

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?

Gives a concrete triggering condition ('when a quarantined memory is valid, e.g., the contradicted belief was wrong'), which is clear context for invocation. It stops short of stating when not to use it or naming an alternative action for invalid memories (e.g., deletion).

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