Skip to main content
Glama

get_quarantined_memories

Read-only

List memories quarantined for contradicting active beliefs, enabling review of flagged items and resolution of conflicts.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already establishes this as a safe read, and the description adds genuinely useful context about why memories end up quarantined (contradicting active beliefs). It says nothing about ordering, whether full memory content is returned, or whether results are trimmable beyond the limit parameter.

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 resource definition front-loaded and the usage hint second; there is minor redundancy between "quarantined" and "flagged" but nothing that wastes the reader's attention.

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 one-parameter, read-only listing tool with no output schema, the definition covers what the tool returns conceptually and when to reach for it. The remaining gap is the absence of any note on result ordering or what a quarantined memory record contains.

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% with a single optional limit parameter already documented as "Maximum results to return," so the schema carries the parameter semantics. The description adds no format, default, or cap details beyond it, which is the expected baseline for a fully documented single-parameter schema.

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 ("List memories") plus the defining condition for inclusion ("quarantined due to contradicting active beliefs"), which separates it from generic listing tools like memory_list. It does not explicitly name the counterpart tools (unquarantine_memory, memory_conflicts), so sibling differentiation is implied rather than stated.

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" gives a general context for invocation, but offers no when-not guidance and does not point to the obvious follow-up or alternative (unquarantine_memory) when a flagged memory should be released. Usage is suggested rather than scoped.

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