CueFrame

List Checkpoints

list_checkpoints

Read-onlyIdempotent

List checkpoint packets newest-first (filter with composeJobId for one run's v1→vN gate history, or projectId). The version stack with per-version status + decisions IS the review history — nothing is deleted.

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

Input Schema

Name	Required	Description
`after`	No	Opaque cursor from the previous page's `pagination.nextCursor`. Forward-only.
`limit`	No	Page size (1..100), default 20. Out-of-range or unparseable clamps into the range.
`projectId`	No	Scope to everything reviewable in one project.
`composeJobId`	No	Scope to ONE compose run — its v1→vN gate history with per-version status and decisions.

Output Schema

Name	Required	Description	Default
`data`	No
`pagination`	No	Cursor pagination metadata.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the result is ordered newest-first, and the version stack is the durable review history with 'nothing is deleted' as a retention guarantee, which tells the agent the listing is historically complete.

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?

Two dense sentences with the core action front-loaded and the filter guidance nested beside it. No filler, though the em-dash aside about review history is slightly compressed and could read as marketing rather than instruction.

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?

An output schema exists and annotations cover the safety profile, so the description is not obligated to explain return shape. What remains slightly missing is how this relates to get_checkpoint for fetching a single packet, and whether the stack is per-packet or flattened.

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% and the param descriptions already spell out 'Scope to ONE compose run — its v1→vN gate history with per-version status and decisions,' which the tool description largely restates. It adds little beyond the schema apart from combining the filters in one sentence.

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 and resource ('List checkpoint packets') plus the ordering ('newest-first'), which is enough to distinguish it from mutation-oriented siblings like apply_composition. It does not name get_checkpoint, the obvious single-item alternative, so the boundary is left implicit.

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 parenthetical explains which filter to pick ('composeJobId for one run's v1→vN gate history, or projectId'), which is useful selection guidance. But it never says when to call this versus get_checkpoint or list_compositions, and gives no prerequisites or exclusions.

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

All CueFrame tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.