Mnemoverse Memory

memory_stats

Read-onlyIdempotent

Retrieve a read-only overview of stored memory, including total entries, learned associations, domain names, and average quality scores to orient before writing or answer recall questions.

Instructions

Get an overview of the stored memory: total count, the number of learned concept associations, the list of domains, and average quality scores. This memory is shared across all AI tools the user has connected to Mnemoverse. Use it to orient yourself, to confirm the exact domain name before writing to it, or when the user asks what you remember. Read-only — changes nothing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`domains`	Yes	User-defined memory domains.
`episodes`	No	Number of individual memories (not merged into a summary).
`prototypes`	No	Number of summary memories merged from several individual ones. Consolidation is not running on the hosted service, so this count does not currently grow.
`avg_valence`	No	Average valence of stored memories: how well recalls turned out, on a scale from -1 to 1.
`memory_count`	Yes	Number of saved memories.
`hebbian_edges`	No	Number of learned concept-to-concept associations; memory_graph reads them.
`avg_importance`	No	Average importance of stored memories, on a scale from 0 to 1.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.14.2Oct 1, 2026

changedOutput schema / properties / episodes / description

Previous value: -"Number of episodic (not yet consolidated) memories."New value: +"Number of individual memories (not merged into a summary)."

changedOutput schema / properties / hebbian_edges / description

Previous value: -"Number of Hebbian concept-to-concept links, learned from concepts that occur together as memories are stored and used."New value: +"Number of learned concept-to-concept associations; memory_graph reads them."

changedOutput schema / properties / prototypes / description

Previous value: -"Number of consolidated prototype memories."New value: +"Number of summary memories merged from several individual ones. Consolidation is not running on the hosted service, so this count does not currently grow."

Changed1 schema field changedv0.11.0Sep 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "avg_importance": {
+      "description": "Average importance of stored memories, on a scale from 0 to 1.",
+      "type": "number"
+    },
+    "avg_valence": {
+      "description": "Average valence of stored memories: how well recalls turned out, on a scale from -1 to 1.",
+      "type": "number"
+    },
+    "domains": {
+      "description": "User-defined memory domains.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "episodes": {
+      "description": "Number of episodic (not yet consolidated) memories.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "hebbian_edges": {
+      "description": "Number of Hebbian concept-to-concept links, learned from concepts that occur together as memories are stored and used.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "memory_count": {
+      "description": "Number of saved memories.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "prototypes": {
+      "description": "Number of consolidated prototype memories.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "memory_count",
+    "domains"
+  ],
+  "type": "object"
+}

First observedv0.3.7Jun 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so 'Read-only — changes nothing' is reinforcement rather than new information. However, the claim that the memory is shared across all connected AI tools is a genuinely useful scope disclosure not present in any structured field.

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 purpose, then scope, then usage, then safety — a sensible order. Three sentences with little waste, though the closing 'Read-only — changes nothing' repeats what the annotations already certify.

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?

For a zero-parameter tool with an output schema and full annotation coverage, the description supplies everything an agent needs: what the call returns, whose data it reflects, and when it is worth calling. No gaps remain.

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 per the rubric the baseline is 4. The description correctly adds background on what the shared store is, which is the only meaningful 'parameter-like' context available for a no-arg call.

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 ('Get an overview of the stored memory') and enumerates exactly what the overview contains: total count, concept associations, domains, average quality scores. It is unambiguous within the sibling set, though it never names a sibling like memory_read or memory_list_recent to draw the boundary 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?

Gives three concrete triggers: orienting yourself, confirming the exact domain name before writing, and answering 'what do you remember'. That is clear when-to-use guidance, but it offers no exclusion or explicit alternative (e.g. use memory_read when you need the raw contents).

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

Deploy Server