Skip to main content
Glama
Sign In
Specky

Specky

by gbb-acelerators
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Checkpoints

sdd_list_checkpoints
Read-onlyIdempotent

List all available checkpoints for a feature, including labels, dates, and phases, to track progress in spec-driven development.

Instructions

Lists all available checkpoints for a feature with their labels, dates, and phases.

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

Input Schema

NameRequiredDescriptionDefault
spec_dirNoSpec directory path.specs
feature_numberNoFeature number (e.g. '001')001

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.4.0-rc.14

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. Description adds value by specifying the returned information (labels, dates, phases), which helps set expectations beyond annotations.

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?

Single sentence, no waste. Front-loaded verb 'Lists' and resource 'checkpoints'. Every word earns its place.

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?

No output schema exists, but description hints at the return structure (labels, dates, phases). Parameter count is low, all documented. Adequate for a simple read-only list tool.

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?

Both parameters (feature_number, spec_dir) are fully described in the input schema with defaults and patterns. The description does not add further meaning, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool 'lists all available checkpoints for a feature' with specific output fields (labels, dates, phases). Distinguishes from sibling tools like sdd_checkpoint (likely singular) and sdd_checklist.

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?

No explicit guidance on when to use this tool versus alternatives, but the context is clear from the description that it's for listing all checkpoints for a feature. Lacks exclusions or when-not-to-use advice.

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

Deploy Server

Other Tools