Skip to main content
Glama
persistent-memory-mcp

persistent-memory-mcp

Check notices

memory_notices
Read-only

Lists artifacts shown in the current session that were later withdrawn, invalidated, or superseded, so you stop relying on them and can check explicitly before a final answer.

Instructions

List the artifacts this session was shown that have since been withdrawn, invalidated or superseded, so you stop relying on them and on what you said from them. Each is reported once. Other tool results already carry new notices as memory_notices; call this when you need to check explicitly, for example before a final answer.

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_notices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, non-destructive, openWorld false). The description adds the behavior the annotations cannot express: each item is reported once, which explains the non-idempotent hint and warns the agent that a second call will not repeat results. It also states the intended effect — stop relying on withdrawn artifacts.

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 sentences, front-loaded with the what and the consequence, followed by the when-to-call rule. Slightly dense phrasing ('and on what you said from them') costs a little clarity but nothing is padding.

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 the return semantics and does so: a list of withdrawn/invalidated/superseded artifacts, deduplicated to one report each. For a zero-parameter read tool this is essentially complete; only the exact item shape is unspecified.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless check by describing session-scoped selection rather than caller-supplied filters.

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 the artifacts this session was shown that have since been withdrawn, invalidated or superseded.' The scope (this session, shown-to-you artifacts) is precise enough to distinguish it from mutation siblings like memory_withdraw, though no sibling is named explicitly.

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?

Explicitly says notices are already delivered passively with other tool results, so this is only needed 'when you need to check explicitly, for example before a final answer.' That is a clear when/when-not rule; it stops short of a 5 because no alternative tool is named for related checks.

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