Skip to main content
Glama
memorysyncio

MemorySync Cursor Starter

Official
by memorysyncio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Save a durable project memory

memorysync_add

Save a single fact, like a project convention or architectural decision, so it persists beyond this conversation and is available to future sessions.

Instructions

Persist one fact so it survives after this conversation ends: an architectural decision, a convention the user asked you to follow, or a constraint that will still be true next session. Call this when the user states a lasting preference or you settle a design question. Do not call it for transient chat, for content already returned by memorysync_search, or for anything a later session would be misled by. Save one discrete fact per call rather than a conversation summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesOne self-contained fact, written so it still makes sense with no surrounding conversation. Write 'This project uses Postgres with SQLAlchemy 2.x', not 'we decided to use that one'. Pronouns and references to the current chat will not resolve in a later session.
sourceNoWhich client or agent observed this fact, used for attribution when two memories conflict. Defaults to 'cursor' if omitted.cursor
metadataNoOptional flat key-value tags used to narrow later searches, for example {"area": "database"}. Values should be short strings. Omit rather than passing an empty object.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIdentifier of the stored memory.
statusYesResult of the write, for example 'created'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.0.2
    • changedInput schema / properties / metadata / description
      Previous value: -"Optional key-value tags, for example {\"area\": \"database\"}, to narrow later searches."New value: +"Optional flat key-value tags used to narrow later searches, for example {\"area\": \"database\"}. Values should be short strings. Omit rather than passing an empty object."
    • addedInput schema / properties / metadata / examples
      Added value: +[
+  {
+    "area": "database"
+  },
+  {
+    "area": "api",
+    "scope": "public"
+  }
+]
    • changedInput schema / properties / source / description
      Previous value: -"Which client or agent observed this, used for attribution when memories conflict."New value: +"Which client or agent observed this fact, used for attribution when two memories conflict. Defaults to 'cursor' if omitted."
    • addedInput schema / properties / source / examples
      Added value: +[
+  "cursor",
+  "claude-code",
+  "ci"
+]
    • changedInput schema / properties / text / description
      Previous value: -"One self-contained fact, written so it still makes sense with no surrounding conversation."New value: +"One self-contained fact, written so it still makes sense with no surrounding conversation. Write 'This project uses Postgres with SQLAlchemy 2.x', not 'we decided to use that one'. Pronouns and references to the current chat will not resolve in a later session."
    • addedInput schema / properties / text / examples
      Added value: +[
+  "This project uses Postgres with SQLAlchemy 2.x",
+  "All API errors must return RFC 7807 problem details"
+]
    • addedInput schema / properties / text / minLength
      Added value: +1
  2. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / metadata / additionalProperties
      Added value: +true
    • changedInput schema / properties / metadata / description
      Previous value: -"Optional key-value metadata dictionary."New value: +"Optional key-value tags, for example {\"area\": \"database\"}, to narrow later searches."
    • changedInput schema / properties / source / description
      Previous value: -"Origin of the memory (default: cursor)."New value: +"Which client or agent observed this, used for attribution when memories conflict."
    • changedInput schema / properties / text / description
      Previous value: -"The exact fact, convention, or architectural decision to persist."New value: +"One self-contained fact, written so it still makes sense with no surrounding conversation."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "id": {
+      "description": "Identifier of the stored memory.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Result of the write, for example 'created'.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "status"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false (write operation), destructiveHint=false, and idempotentHint=false. The description adds valuable context: the fact persists across sessions and must be self-contained to avoid misleading later sessions. It also emphasizes durability without contradicting any annotation. The bar is lower due to annotations, but the description adds meaningful behavioral detail beyond them.

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?

The description is about 80 words and every sentence serves a purpose: it states the core function, provides trigger conditions, lists exclusions, and gives a structural guideline (one fact per call). It is front-loaded with the primary purpose and avoids fluff.

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?

The tool has an output schema, so return values are defined elsewhere. The description fully specifies when to use it, what to persist, and how to structure the call. It covers all necessary operational guidance for an agent to invoke it correctly, leaving no critical information 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 coverage is 100% with thorough descriptions for all three parameters, including examples for text and metadata. The description reinforces the text parameter's requirement for self-contained facts but does not add parameter-specific semantics beyond what the schema already provides. Baseline 3 is appropriate given the high schema coverage.

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?

The description uses a specific verb ('Persist') and a clear resource ('one fact') that survives conversation end, with concrete examples of valid facts (architectural decision, convention, constraint). It explicitly distinguishes itself from siblings by stating not to call for content already returned by memorysync_search, making its purpose unambiguous.

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?

It gives explicit call conditions ('Call this when the user states a lasting preference or you settle a design question') and clear exclusions ('Do not call it for transient chat, for content already returned by memorysync_search, or for anything a later session would be misled by'). It also instructs to save one discrete fact per call, fully covering when and when not to use it.

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