Skip to main content
Glama
Sign In
M3 Memory

M3 Memory

by skynetcmd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_get

Read-only

Retrieve a complete memory item by full UUID or 8-character prefix; ambiguous prefixes return an error listing matching IDs.

Instructions

Retrieves a full MemoryItem; accepts full UUID or 8-char prefix; ambiguous prefixes return an error.

Input Schema

NameRequiredDescriptionDefault
idYesMemory item id — 36-char UUID or 8-char prefix. Ambiguous prefixes return an error listing the matching ids.
storeNoNamed store for this call only: main, or a [stores.<name>] in m3_config.toml.
timeoutNoPer-call timeout in seconds; <=0 disables.
databaseNoSQLite file for this call only (legacy; prefer store). SQLite backend only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.1.21
    • removedInput schema / properties / database / default
      Removed value: -""
    • addedInput schema / properties / database / description
      Added value: +"SQLite file for this call only (legacy; prefer store). SQLite backend only."
    • removedInput schema / properties / database / title
      Removed value: -"Database"
    • addedInput schema / properties / id / description
      Added value: +"Memory item id — 36-char UUID or 8-char prefix. Ambiguous prefixes return an error listing the matching ids."
    • removedInput schema / properties / id / title
      Removed value: -"Id"
    • addedInput schema / properties / store
      Added value: +{
+  "description": "Named store for this call only: main, or a [stores.<name>] in m3_config.toml.",
+  "type": "string"
+}
    • removedInput schema / properties / timeout / default
      Removed value: -30
    • addedInput schema / properties / timeout / description
      Added value: +"Per-call timeout in seconds; <=0 disables."
    • removedInput schema / properties / timeout / title
      Removed value: -"Timeout"
    • removedInput schema / title
      Removed value: -"memory_getArguments"
  2. Addedv0.1.9
  3. Removedv0.1.6
  4. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / timeout
      Added value: +{
+  "default": 30,
+  "title": "Timeout",
+  "type": "number"
+}
  5. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered by structured data. The description adds non-obvious behavior: prefix matching is accepted and ambiguous prefixes produce an error rather than a partial or arbitrary result. It omits behavior for missing ids or how the per-call timeout/database options interact, but the extra context is genuinely useful.

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?

A single compact sentence with the core action front-loaded, followed by two clauses that each carry distinct information (accepted formats, ambiguity handling). No filler whatsoever.

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 read-only single-item fetch with fully described parameters and no output schema, the description covers what is returned ('full MemoryItem') and the key failure mode. A brief note on not-found behavior or that the full item includes its metadata would close the remaining gap.

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 every parameter including the id prefix rule, store, timeout, and database is already documented. The description restates the id format and ambiguity rule rather than adding new semantics, so baseline 3 applies.

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 ('Retrieves') and a specific resource ('a full MemoryItem'), with 'full' implicitly contrasting against the partial results you'd get from the sibling memory_search. It stops short of naming that sibling explicitly, but the retrieval semantics are unambiguous.

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?

Usage is only implied: it's clear you need an id, but there is no statement of when to choose this over memory_search or chatlog_search, nor any prerequisite about knowing the id in advance. An agent can infer the intent but has no explicit routing rule.

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