Skip to main content
Glama
ManuelWarland

MemCore

by ManuelWarland
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get one entry

memory_get
Read-onlyIdempotent

Retrieve the full, current content of one stored memory entry by its exact scope and name, so you can confirm details before relying on them. Returns null if missing or archived.

Instructions

Fetch one memory entry, complete, by its exact scope and name.

Use it when you already know both keys (from memory_search, memory_list or memory_recent results) and need the full, current content before relying on it. Returns null when no entry has that scope and name, or when it is archived and include_archived is false. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesEntry name: the short kebab-case slug that identifies the entry within its scope.
scopeYesProject/topic scope the entry belongs to, e.g. a project folder name (list them with memory_scopes). On a scope-locked connection (--scope), this argument is ignored and the connection's own scope is used.
include_archivedNoAlso return archived (soft-deleted) entries. Default false: archived entries are hidden.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • addedInput schema / properties / include_archived / description
      Added value: +"Also return archived (soft-deleted) entries. Default false: archived entries are hidden."
    • addedInput schema / properties / name / description
      Added value: +"Entry name: the short kebab-case slug that identifies the entry within its scope."
    • addedInput schema / properties / scope / description
      Added value: +"Project/topic scope the entry belongs to, e.g. a project folder name (list them with memory_scopes). 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, so the safety profile is covered. The description adds genuinely new behavioral context: it returns null for unknown scope/name and hides archived entries unless include_archived is true. It stops short of describing other edge behavior (e.g. scope-locked connections), but this is solid added value beyond annotations.

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?

Two short sentences, front-loaded with the core action, followed immediately by the selection condition. Every clause earns its place with no filler.

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?

With an output schema present and annotations covering the safety profile, the description only needs to supply the ambiguous edge cases — and it does: the null return for missing entries and the archive-hiding default. Nothing an agent needs to invoke this correctly is missing.

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 all three parameters are already documented at the field level (including the kebab-case name convention and the --scope override). The description only echoes 'exact scope and name' and the archived gating, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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 and resource ('Fetch one memory entry, complete, by its exact scope and name'), which cleanly distinguishes a keyed single-item get from list/search/recent siblings. The 'complete' qualifier signals it returns full content rather than a summary.

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?

Explicitly states the precondition ('when you already know both keys'), names where those keys come from (memory_search, memory_list, memory_recent), and gives the motivating purpose ('need the full, current content before relying on it'). No inference required.

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