Update the last-accessed timestamp of a memory by its ID to preserve recency without altering its content or creation date.
Bump a memory's recency (last-accessed timestamp) without changing its content, id, or createdAt.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Memory ID to touch |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes side effects (bump timestamp) and non-effects (no changes to content, id, or createdAt). Lacks details on error handling or authentication, but acceptable for a simple tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Concise, one-sentence description with clear structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for basic use, but lacks information on return value or error behavior if ID not found.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema describes 'id' as 'Memory ID to touch', which is clear. The description reinforces that it's the identifier.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the function: updates last-accessed timestamp, and explicitly excludes changes to content, id, or createdAt.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Does not provide guidance on when to use this tool versus alternatives; only states what it does.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
This server cannot be deployed