Skip to main content
Glama

get_checkpoint_log

Review recent checkpoint history to see when memories last synced and what changed; use it to check memory freshness or debug sync issues.

Instructions

Show recent checkpoint history for the memory store — when memories were last synced and what changed. CALL THIS: to understand how fresh the memory store is, or to debug sync issues.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_checkpoint_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax checkpoints to return (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.3

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. "Show" implies a read-only, non-mutating call, and the mention of sync freshness and changes adds useful context, but it says nothing about ordering (only the word "recent" hints at newest-first), whether output is truncated, or permissions.

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: the first defines what is returned, the second front-loads the usage triggers. There is no redundant or filler wording.

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 single-parameter, read-only inspection tool with no output schema, the description covers purpose, return content, and when to call it. Only minor gaps remain, such as ordering and output size behavior, which do not block correct invocation.

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% for the single optional limit parameter with a documented default, so the schema already does the explanatory work. The description's word "recent" reinforces recency ordering but adds no detail on the limit's effect beyond what the schema states; baseline 3 applies.

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 gives a specific verb ("Show") and resource ("recent checkpoint history for the memory store") and explains what a checkpoint contains (when memories were last synced, what changed). That is enough to separate it from get_memory or list_memories, which deal with current memories rather than history, though no sibling is named explicitly.

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 "CALL THIS:" clause states two concrete triggers: gauging freshness of the memory store and debugging sync issues. It gives no when-not-to-use guidance or named alternative for reading current memory contents, so it stops short of a 5.

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