MemorySync Cursor Starter

Official

by memorysyncio

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Read one memory in full

memorysync_get

Read-only

Retrieve a complete memory record by its ID, including text, tags, importance, and timestamps, to verify relevance or check if a fact is stale after a search.

Instructions

Fetch the complete stored record for a single memory id, including its text, tags, importance and timestamps. Use this after memorysync_search when a result looks relevant but the snippet is not enough to act on, or when you need the creation date to judge whether a fact is stale. Takes an id, not a search phrase - to find a memory by topic, call memorysync_search first and pass an id from its results.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`memory_id`	Yes	Identifier of the memory to read, taken from the id field of a memorysync_search result.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Identifier of the memory.
`tags`	No	Tags attached to this memory.
`text`	Yes	The stored fact in full.
`created_at`	No	When the fact was first observed, for judging staleness.
`importance`	No	Importance score used in ranking.
`updated_at`	No	When the record last changed.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.3Sep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already convey readOnlyHint and openWorldHint, lowering the bar. The description adds useful behavioral context by stating it returns the complete record with specific fields, and clarifies that it does not perform search. No contradiction with annotations.

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?

Three sentences with no filler: first states what the tool does, second gives concrete use cases, third clarifies the id requirement and routing to the sibling. Every sentence earns its place and the most important information is front-loaded.

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 single-parameter read tool with a rich schema, annotations, and an output schema, the description covers purpose, usage timing, alternative routing, and parameter semantics. Nothing essential for correct invocation is 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%, so the schema already documents memory_id thoroughly. The description reinforces that the id comes from memorysync_search and must not be a search phrase, which adds operational nuance but no new format or syntax details beyond the schema.

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 ('Fetch') and names the exact resource ('complete stored record for a single memory id'), then lists the fields returned. It clearly distinguishes itself from memorysync_search by emphasizing this takes an id, not a search phrase.

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?

The description explicitly states when to use this tool: after memorysync_search when a snippet is insufficient, or when needing creation date to assess staleness. It also gives a clear exclusion, directing users to memorysync_search for topic-based lookup, and names the alternative.

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

Deploy Server