AI Workspace Kit

workspace_checkpoint

Idempotent

Preserve shared project memory by saving a strict, verified summary checkpoint locally instead of raw chat. Supports idempotent, secure context handoff across Codex, ChatGPT, and Aside.

Instructions

Save a strict v1 confirmed_summary checkpoint locally; never raw chat. Required keys: version=1, source=chatgpt|codex|manual|aside, session, checkpoint, stamp with timezone, kind=confirmed_summary, verified=true, explicit_memory boolean, next_context short text, memory object. memory requires topic/repo slugs, business boolean, sensitive=false, and arrays context/status/decisions/todo/failed_approaches/links/completed_todo. No secrets, personal data or local paths. Stable session/checkpoint IDs ensure idempotency. Existing scheduler handles promotion; this call does not publish.

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": "workspace_checkpoint"
  }
}

Input Schema

Name	Required	Description	Default
`checkpoint`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 29, 2026

TDQS

A4.2/5.0

Behavior5/5

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

With annotations covering safety (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description adds substantial context: local-only saving, data hygiene rules (no secrets, personal data, or local paths), idempotency via stable IDs, and non-publishing behavior handled by a scheduler.

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?

The description is front-loaded with the core action and then flows through requirements, constraints, and behavior. It is dense but every sentence adds necessary specification, though a bulleted format could improve readability.

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?

Given the output schema and annotations, return values and safety profiles are covered elsewhere. The description thoroughly explains payload structure and behavior, but leaves slight ambiguity about whether the single 'checkpoint' parameter is an object containing the listed keys or a simpler value.

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

Parameters5/5

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

Schema description coverage is 0% and the sole parameter has no type or description, so the description carries full burden. It enumerates required keys, enums, boolean constraints, and array structures in detail, adding clear meaning beyond the empty schema.

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 states a specific verb (Save) and resource (strict v1 confirmed_summary checkpoint) with a clear exclusion (never raw chat). It distinguishes from publishing and implies difference from recall/read siblings, but does not explicitly name any sibling for routing.

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?

It implies usage by specifying what to save and what not to save ('never raw chat', 'does not publish'), but gives no explicit when-to-use context or named alternatives to workspace_recall or other siblings.

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

Deploy Server