Skip to main content
Glama
Sign In
callimachus

callimachus

by BetaBots-LLC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

load_snapshot

Read-only

Resume a saved AI coding session by loading its project memory and transcript as markdown, trimmed to a character budget so you can continue the work.

Instructions

Load a saved snapshot (project memory plus transcript) as markdown to continue that session, trimmed to budget chars (default 24000); text and structured markdown both hold it. Id from list_snapshots.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesSnapshot id from list_snapshots or snapshot_session.
budgetNoMax chars to return (default 24000, max 96000).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "id": {
+          "type": "integer"
+        },
+        "markdown": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "markdown"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "notice": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "notice"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}
  2. Changed4 schema fields changedv0.11.3
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / budget
      Added value: +{
+  "description": "Max chars to return (default 24000, max 96000).",
+  "format": "uint32",
+  "minimum": 0,
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • changedInput schema / properties / id / description
      Previous value: -"The snapshot id (from list_snapshots or snapshot_session)."New value: +"Snapshot id from list_snapshots or snapshot_session."
    • removedInput schema / title
      Removed value: -"LoadSnapshotArgs"
  3. Addedv0.6.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a safe read operation (readOnlyHint true, openWorldHint false), so the description adds useful non-obvious behavior: the result is trimmed to `budget` characters, defaulting to 24000, and appears in both the text content and a structured `markdown` field. It does not describe truncation signaling or what happens if the snapshot is missing, but the added context is meaningful.

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?

A single dense sentence that front-loads the verb and the payload, with the budget and id-source details trailing. It is slightly compressed by the parenthetical and dual-field clause, but no sentence is wasted.

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?

With an output schema present and full parameter documentation, the description supplies the remaining operational facts an agent needs: what a snapshot contains, how the size cap applies, and where the id comes from. Nothing essential to 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 both parameters are already documented, including the default and max for `budget`. The description restates the budget trimming behavior rather than adding syntax or edge-case meaning, so the baseline of 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?

Names a specific verb and resource ('Load a saved snapshot') and clarifies the payload ('project memory plus transcript') and output form ('as markdown'). It distinguishes itself implicitly from the listing sibling by pointing to list_snapshots for ids, though it does not explicitly contrast with snapshot_session.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The stated intent 'to continue that session' and 'Id from list_snapshots' give an implied when-to-use and where the id comes from. There is no explicit exclusion or alternative path (e.g., when to use thread/memory tools instead), so guidance remains implied rather than directive.

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