Skip to main content
Glama
kunickiaj

codemem

by kunickiaj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

memory_remember

Save coding milestones, decisions, and facts as structured memories with kind, title, body, and optional project and confidence. Use to preserve context and enable retrieval in future sessions.

Instructions

Create a new memory. Use for milestones, decisions, and notable facts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesBody text (high-signal content)
kindYesMemory kind
titleYesShort title
projectNoProject identifier
confidenceNoConfidence 0-1

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.44.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, and the description's 'Create a new memory' is consistent with those. The description adds little behavioral detail beyond that—no mention of persistence, side effects, or availability—though the existing annotations carry most of the safety burden.

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 with a clear verb-first structure; the core action is front-loaded and there is no filler. Every sentence earns its place.

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 simple create tool with full schema coverage, an output schema, and annotations, the description is nearly complete. The main gap is that it never addresses the related memory_learn tool, which could leave an agent unsure which creation route to use.

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 the schema already documents all five parameters, including the kind enum and confidence range. The description's use cases hint at suitable memory content but do not add meaningful parameter-level detail beyond the schema.

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 opens with a specific verb and resource ('Create a new memory') and gives concrete use cases ('milestones, decisions, and notable facts'). It is clear, but it does not explicitly distinguish itself from the similarly named sibling memory_learn, so it falls short of full sibling differentiation.

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?

It provides explicit usage context: 'Use for milestones, decisions, and notable facts.' However, it does not say when not to use this tool or name an alternative such as memory_learn or memory_get, so the when-not guidance is missing.

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