Skip to main content
Glama

unquarantine_memory

Release a quarantined memory back into active use when it proves valid, such as when the contradicted belief was wrong.

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": "unquarantine_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_hashYesContent hash of the quarantined memory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, so the description must carry most of the behavioral load. It communicates the state transition out of quarantine and the judgment criterion, but not what happens to the memory afterwards (does it rejoin search results? does the conflict record persist? is the release reversible?), nor any permission expectations.

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, action first and condition second, with zero filler. Nothing could be removed without losing signal.

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

Completeness3/5

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

For a one-parameter mutation with no output schema, the definition covers what it does and when, but leaves the resulting state and any return value unexplained. An agent would need to guess whether the released memory is immediately searchable or whether a conflict entry is retained.

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% and the single parameter content_hash is fully documented in the schema. The description adds no format or sourcing detail beyond implying the hash identifies a quarantined memory, so the baseline of 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?

The description gives a specific verb and resource: 'Release a memory from quarantine.' That is unambiguous and distinguishable from siblings like memory_delete or memory_resolve, though it never explicitly contrasts itself with memory_resolve, which an agent might reasonably consider an alternative.

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?

'Use when a quarantined memory is valid (e.g., the contradicted belief was wrong)' supplies a concrete triggering condition with a worked example. It stops short of stating when NOT to use it (e.g., still-contradicted memories, or using memory_delete instead) and names no alternative tool.

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