Skip to main content
Glama
ManuelWarland

MemCore

by ManuelWarland
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Audit log

memory_events
Read-onlyIdempotent

Read the append-only audit log of memory changes, newest first, to see who wrote, updated, archived, or restored what, when, from which client, and why; includes conflicts and secret redactions.

Instructions

Read the append-only audit log, newest first: who wrote, updated, archived or restored what, when, from which client, and any conflicts or secret redactions.

Use it to answer "who changed this, and why?". To see the previous CONTENT of an entry, use memory_history instead; for the latest entries themselves, memory_recent. Read-only and available on any connection; scope-locked connections only see their own scope's events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOnly events about this entry name. Omit for every entry.
limitNoMaximum number of events to return (default 50). Values are clamped to 1-200.
scopeNoRestrict to one project/topic scope (list them with memory_scopes). Omit to cover every scope. On a scope-locked connection (--scope), this argument is ignored and the connection's own scope is used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of events to return (default 50). Values are clamped to 1-200."
    • addedInput schema / properties / name / description
      Added value: +"Only events about this entry name. Omit for every entry."
    • addedInput schema / properties / scope / description
      Added value: +"Restrict to one project/topic scope (list them with memory_scopes). Omit to cover every scope. On a scope-locked connection (--scope), this argument is ignored and the connection's own scope is used."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds real context: the log is append-only, results are newest-first, and scope-locked connections only see their own scope's events — none of which the annotations convey.

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?

Three tight sentences, front-loaded with the core verb and content, then routing guidance, then execution constraints. No filler and each sentence carries distinct information.

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

Completeness5/5

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

An output schema exists so return shape needn't be explained, and the annotations carry the safety profile. The description still covers ordering, scope-visibility edge cases, and sibling routing, leaving nothing an agent needs to call it correctly.

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%, so name, limit (with clamping to 1-200), and scope are already fully documented in the schema. The description adds no parameter-level detail, so this sits at the baseline for high-coverage schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (read) and resource (append-only audit log), then enumerates exactly what the log records: who wrote/updated/archived/restored what, when, from which client, plus conflicts and secret redactions. It explicitly distinguishes itself from the sibling tools it could be confused with (memory_history, memory_recent).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete triggering question ("who changed this, and why?") and names two alternatives with the condition that selects each: memory_history for previous CONTENT, memory_recent for the latest entries themselves. This is explicit when/when-not/alternative guidance.

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

Deploy Server

Other Tools