Skip to main content
Glama
ManuelWarland

MemCore

by ManuelWarland
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Browse entries

memory_list
Read-onlyIdempotent

Browse stored memories by scope, type, or archived state without a search query. Use it to view all project entries, filter items by type, or find archived memories ready to restore.

Instructions

Browse entries by scope, type and archived state, WITHOUT a search query.

Use it to see everything in a project scope (onboarding to a codebase), every entry of one type (e.g. all feedback), or what has been archived (candidates for memory_restore). To find entries by content use memory_search; for the latest changes, memory_recent. Read-only. An invalid type returns [{"error": ...}].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOnly entries of this type: user, feedback, project or reference. Omit for every type.
limitNoMaximum number of entries to return (default 100). 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.
archivedNoIf true, return ONLY archived entries instead of active ones. Default false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • addedInput schema / properties / archived / description
      Added value: +"If true, return ONLY archived entries instead of active ones. Default false."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of entries to return (default 100). Values are clamped to 1-200."
    • 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."
    • addedInput schema / properties / type / description
      Added value: +"Only entries of this type: user, feedback, project or reference. Omit for every type."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description redundantly restates 'Read-only' but adds a genuinely useful behavioral detail, the invalid-type error shape ([{"error": ...}]). It stops short of describing pagination or result volume behavior for a listing tool.

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?

Front-loaded with the core scoping constraint 'WITHOUT a search query' and tightly ordered: what it does, when to use it, alternatives, then an edge-case note. Slightly bloated by the 'Read-only' line, which only repeats the readOnlyHint annotation.

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 is present, so return-value documentation is unnecessary, and the description covers purpose, alternatives, edge-case error behavior and read semantics. Nothing an agent needs to select or call this listing tool is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by framing the archived flag as 'candidates for memory_restore' and the scope filter as 'everything in a project scope'. The remaining parameters (type, limit) are left to the schema, which documents them adequately.

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 (browse) plus the resource (entries) and the exact filters it operates on (scope, type, archived state), and explicitly contrasts itself with search-based retrieval. An agent can distinguish this from memory_search without opening either schema.

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 three concrete when-to-use scenarios (project onboarding, single-type listing, archived entries for memory_restore) and explicitly routes content-based lookup to memory_search and latest-change lookup to memory_recent. Exclusions and alternatives are both named.

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