Skip to main content
Glama

memory_quarantine_list

Read-only

Lists quarantined memories that conflict with active beliefs so you can review flagged entries and resolve contradictions.

Instructions

List memories that have been quarantined due to contradicting active beliefs. Use to review flagged memories.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_quarantine_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv13.0.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description's credit comes from explaining what "quarantined" means (contradicting active beliefs), which is genuinely useful context. It does not disclose ordering, whether the full record or only a summary is returned, or how the default limit of 50 interacts with paging.

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?

Two short sentences with the core purpose front-loaded and no wasted preamble. The second sentence largely restates the first ("review flagged memories"), adding little beyond a usage hint.

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 read-only, single-parameter list tool with annotations and no output schema, the definition covers the essential who/what. It leaves the agent without guidance on result ordering, volume expectations, or the natural follow-up path (release vs. resolve), which is a noticeable gap for a workflow-oriented tool family.

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 limit parameter is already documented with its default, so the schema carries the parameter burden. The description adds no meaning about how results are ordered or truncated when limit is hit, 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?

The description states a specific verb and resource ("List memories") plus a precise scope (those "quarantined due to contradicting active beliefs"), which clearly separates it from memory_list and from the mutating sibling memory_quarantine_release. It stops short of naming an alternative explicitly, so it doesn't reach the top band.

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?

"Use to review flagged memories" implies the review/inspection scenario, but gives no exclusion or routing guidance — nothing tells the agent when to prefer memory_conflicts or memory_quarantine_release instead, nor what prerequisite state (quarantined items existing) is required.

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