Loading ToolBench
Freeze and restore your developer context when switching branches: git state, last failing command, and your intent.
ContextResume defines 3 tools with clear verb-noun naming (get_context, list_snapshots, save_snapshot) and reasonable descriptions (avg 150 chars). All tools have input schemas with Zod validation and parameter descriptions. However, output schemas are undocumented, callers cannot predict response structure. Error handling returns plain text without recovery guidance. No tool annotations (readOnlyHint/destructiveHint) despite clear read/write semantics. Parameter descriptions are adequate but lack format constraints (e.g., 'Absolute path' should specify format or validation rules). Missing pagination for list_snapshots despite potentially returning many branches.
Read the saved ContextResume snapshot for a branch: intent, last failing command, error, changed files, recent commands, and a diff excerpt, as markdown.
List the latest snapshot of every branch as JSON, for one repository or for all of them.
Freeze the current context of a repository with an optional note describing what you were doing.
Output schemas undocumented. get_context returns markdown text, list_snapshots returns JSON with unspecified structure, save_snapshot returns plain text. LLMs cannot predict response fields for downstream chaining.
No tool annotations. save_snapshot is destructive (writes state) and get_context/list_snapshots are read-only, but no destructiveHint or readOnlyHint declared. Agents cannot distinguish safe from unsafe operations.
Error responses lack recovery guidance. errorResult() returns raw error messages without suggesting next steps. E.g., 'No snapshot for main in /repo' should suggest 'Run save_snapshot first' or 'Call list_snapshots to see available branches'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
list_snapshots lacks pagination. No limit, offset, or cursor parameters. If many branches exist, response could be very large and blow context window. Should cap results and offer pagination.
Parameter descriptions lack format constraints. 'Absolute path to a git checkout' should specify validation (e.g., 'must exist and be a valid git repository') or reference a pattern.