Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

List blog design checkpoints

blog_design_checkpoint_list
Read-onlyIdempotent

List all checkpoints of a design. The oldest checkpoint is the saved version. Newer checkpoints are unsaved versions of the same design.

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": {
      "DesignID": "<DesignID>"
    },
    "name": "blog_design_checkpoint_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
DesignIDYesDesign UUID whose checkpoints to list.

Output Schema

NameRequiredDescriptionDefault
CheckpointsYesCheckpoints of one design, oldest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The readOnly/idempotent/non-destructive annotations already cover the safety profile, and the description adds genuinely non-obvious semantics: the oldest entry is the persisted version while newer entries are unsaved drafts of the same design. That is real behavioral context an agent could not derive from the annotations or schema, though pagination or result-size behavior is not mentioned.

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?

Three short sentences with zero filler; the core action is front-loaded and the two explanatory sentences about checkpoint ordering each carry distinct information.

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?

With an output schema present and annotations covering safety, the description plus structured data are enough to call this single-parameter read correctly. The only remaining gap is the missing routing guidance versus the latest-checkpoint sibling, which belongs to usage rather than completeness.

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 DesignID property is described as the design UUID whose checkpoints to list, so the description need not repeat it. It adds no further parameter meaning, so the 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?

The description uses a specific verb and resource ("List all checkpoints of a design") that matches the tool name and makes the operation unambiguous. It does not, however, distinguish itself from the closely related sibling blog_design_get_latest_checkpoint or explain how it relates to blog_design_checkpoint_restore, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or named alternative. The ordering explanation hints that this is for inspecting history (e.g. before a restore), but the agent receives no guidance on choosing this over blog_design_get_latest_checkpoint.

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

All GoodSender toolsInspect
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.

Resources