Skip to main content
Glama

Restore context

restore_context
Destructive

Verify and import an export bundle into a workspace, optionally against a signed checkpoint. Requires scope 'context:restore'.

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": {
      "workspace_id": "<workspace_id>",
      "bundle": "<bundle>"
    },
    "name": "restore_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleYesA bundle returned by export_context.
checkpointNoOptional signed checkpoint from create_checkpoint. When given, the restore proceeds only if the signature verifies, the checkpoint belongs to this account, and every memory in the bundle matches the checkpoint's content hash.
on_conflictNoskip
workspace_idYes
idempotency_keyNoOptional. Same key + same arguments within 24 h returns the original result.
require_signed_checkpointNoReject unsigned context imports, rather than only checking the bundle's editable SHA-256 digest. Requires a valid same-account signed checkpoint.
require_complete_checkpointNoWhen checkpoint is supplied, require every signed memory key to be present exactly once in this bundle. Set true for a complete restore; false permits an explicitly reported partial/page restore.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / require_complete_checkpoint
      Added value: +{
      +  "default": false,
      +  "description": "When checkpoint is supplied, require every signed memory key to be present exactly once in this bundle. Set true for a complete restore; false permits an explicitly reported partial/page restore.",
      +  "title": "Require Complete Checkpoint",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / require_signed_checkpoint
      Added value: +{
      +  "default": false,
      +  "description": "Reject unsigned context imports, rather than only checking the bundle's editable SHA-256 digest. Requires a valid same-account signed checkpoint.",
      +  "title": "Require Signed Checkpoint",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is known. The description adds useful context about signature/hash verification and the required scope, but it never says what gets destroyed or overwritten in the target workspace (e.g. the effect of on_conflict='overwrite' on existing memories), which is the key risk for a destructive import.

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 sentences, zero waste: the core action and its verification behavior come first, the permission prerequisite last. Nothing is repeated from the title or 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 7-parameter destructive tool with nested objects and no output schema, the description leaves out what the restore returns (the schema hints at an 'explicitly reported partial/page restore' result) and what existing workspace content is affected. Adequate but with clear gaps given the tool's complexity.

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 description coverage is 71%, and the schema itself explains checkpoint, idempotency_key and the two require_* flags in depth. The description adds no parameter meaning beyond that, and the enum parameter on_conflict ('skip' vs 'overwrite') is undocumented in both places. 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?

States a specific verb pair and resource: 'Verify and import an export bundle into a workspace', plus the optional signed-checkpoint variant. An agent can immediately tell this is the inverse of export_context. It stops short of explicitly naming a sibling tool or contrasting scope, so it is clear but not maximally differentiated.

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?

Gives one concrete prerequisite ('Requires scope context:restore') and notes the checkpoint is optional, which implies the tool is used to re-import a previously exported bundle. It never states when to prefer this over alternatives or when not to call it, leaving usage to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources