codemem

Overview Schema Source Related Servers Discussions Admin

memory_learn

Read-only

Starts the codemem memory learning process to understand available tools; call it first when starting a new session to get practical usage guidance, avoiding trial and error.

Instructions

Learn how to use codemem memory tools. Call this first if unfamiliar.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`intro`	Yes
`forget`	Yes
`recall`	Yes
`client_hint`	Yes
`persistence`	Yes
`prompt_hint`	Yes
`recommended_system_prompt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.44.2Sep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "client_hint": {
+      "type": "string"
+    },
+    "forget": {
+      "additionalProperties": {},
+      "properties": {
+        "examples": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "how": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "when": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "when",
+        "how",
+        "examples"
+      ],
+      "type": "object"
+    },
+    "intro": {
+      "type": "string"
+    },
+    "persistence": {
+      "additionalProperties": {},
+      "properties": {
+        "examples": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "how": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "when": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "when",
+        "how",
+        "examples"
+      ],
+      "type": "object"
+    },
+    "prompt_hint": {
+      "type": "string"
+    },
+    "recall": {
+      "additionalProperties": {},
+      "properties": {
+        "examples": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "how": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "when": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "when",
+        "how",
+        "examples"
+      ],
+      "type": "object"
+    },
+    "recommended_system_prompt": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "intro",
+    "client_hint",
+    "recall",
+    "persistence",
+    "forget",
+    "prompt_hint",
+    "recommended_system_prompt"
+  ],
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description doesn't contradict them. The description adds that it is a learning/instruction tool, which is mild behavioral context, but does not specify what the agent will actually receive from it. Given annotations, this is acceptable.

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, zero fluff. The purpose is in the first line and the usage guidance in the second. This is as lean as a description can be.

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?

Given the tool has no parameters and has an output schema, the description is sufficient for a call-first help tool. It could mention what the output format is, but the presence of a schema covers that, and the simple nature of this tool does not demand more.

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 has 0 parameters, so the input schema carries no information to enhance. Per the rubric, a no-parameter tool starts at 4, and the description doesn't need to add parameter details that simply don't exist.

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?

The description clearly states the tool's purpose: 'Learn how to use codemem memory tools'. The verb 'learn' plus resource and the specific 'first if unfamiliar' hint distinguish it from the sibling tools like memory_search and memory_schema, although it doesn't explicitly name a non-overlap.

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?

The description explicitly says 'Call this first if unfamiliar', giving a clear condition for when to invoke this tool. It does not list alternatives or state when not to use it, but the 'first' ordering provides enough guidance for a meta/help tool.

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

Deploy Server