Skip to main content
Glama
Chaerulcp

shared-agent-memory-mcp

by Chaerulcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

memory_recent

List recently updated memories from the shared Notion memory to get context about what was learned or saved. Optionally filter by project or agent.

Instructions

List the most recently updated memories from the shared Notion memory. Set response to compact to return excerpts without full content. Use to get context about what was learned/saved lately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNo
limitNo
projectNoOnly memories for this project/repository
responseNoCompact omits full content; full preserves the existing responsefull
currentProjectNoUse the current Git repository as project scope when project is omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.6.0
    • addedInput schema / properties / currentProject
      Added value: +{
+  "default": false,
+  "description": "Use the current Git repository as project scope when project is omitted",
+  "type": "boolean"
+}
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Only memories for this project/repository",
+  "maxLength": 120,
+  "type": "string"
+}
    • addedInput schema / properties / response
      Added value: +{
+  "default": "full",
+  "description": "Compact omits full content; full preserves the existing response",
+  "enum": [
+    "full",
+    "compact"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

There are no annotations, so the description must carry behavior. It states the response-mode behavior (compact returns excerpts) and 'List' implies a read-only operation, but it does not explicitly confirm no side effects, mention auth/access needs, or describe ordering guarantees beyond 'recently updated.'

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?

Three short sentences, front-loaded with the main operation; each adds some value. The compact-mode tip and use-case sentence are useful but mildly redundant with the first sentence and schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-output-schema tool with 5 optional params, the description gives the core list behavior and response modes, but omits what an actual result item looks like, default agent scope, and the meaning of 'full' vs 'compact' beyond omission. It is adequate for a simple list but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 60% schema coverage, the schema documents project, response, and currentProject, but not agent or limit. The description only adds a usage tip for response ('compact... without full content'), which largely repeats the schema, and does not explain the agent scope or default limit.

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 opening sentence names a specific verb ('List') and resource ('most recently updated memories from the shared Notion memory'), so an agent immediately knows the operation and scope. The recency qualifier separates it from sibling search/get tools, even though no sibling is named.

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 last sentence gives a concrete use case: 'Use to get context about what was learned/saved lately.' That is clear context for when to call it, but it does not explicitly contrast with memory_search or memory_get or mention any exclusions.

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