Clink MCP Server

add_checkpoint

Add a checkpoint to a milestone for tracking progress, specifying dependencies, and linking to Git resources like branches, PRs, or commits.

Instructions

Add a new checkpoint to an existing milestone. Optionally specify a position to insert at, or it will be appended at the end.

    Args:
        milestone_id: The milestone ID
        title: Checkpoint title
        description: Checkpoint description (optional)
        requires_consensus: If true, requires group vote before completion (optional)
        depends_on: Dependencies. Use number for same-milestone (e.g., 1), or "milestone_id:order" for cross-milestone (e.g., "ms_abc123:4"). Same-milestone deps must reference earlier checkpoints.
        git_branch_url: Git branch URL (full URL)
        git_pr_url: Git pull request URL (full URL)
        git_commit_url: Git commit URL (full URL)
        position: Position to insert at (1-based). If not provided, appends at end.

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": {
      "milestone_id": "<milestone_id>",
      "title": "<title>"
    },
    "name": "add_checkpoint"
  }
}

Input Schema

Name	Required	Description	Default
`milestone_id`	Yes
`title`	Yes
`description`	No
`requires_consensus`	No
`depends_on`	No
`git_branch_url`	No
`git_pr_url`	No
`git_commit_url`	No
`position`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jan 29, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It mentions that checkpoints can be inserted at specific positions or appended, but doesn't disclose permission requirements, whether this is a write operation, what happens on success/failure, or how dependencies affect workflow. For a creation tool with 9 parameters, this is insufficient disclosure.

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 appropriately sized with a clear purpose statement followed by well-structured parameter documentation. Every sentence adds value, though the parameter documentation could be slightly more concise. The structure is logical with purpose first, then detailed args.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 parameters, creation operation) and the presence of an output schema, the description covers parameter semantics well but lacks behavioral context about permissions, side effects, and error conditions. The output schema existence reduces the need to describe return values, but more operational guidance would be helpful for this mutation tool.

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?

With 0% schema description coverage, the description fully compensates by providing detailed semantic explanations for all 9 parameters. It clarifies optional vs required parameters, explains dependency formats ('milestone_id:order' for cross-milestone), specifies position numbering (1-based), and documents default behaviors (appends at end if position not provided).

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?

The description clearly states the specific action ('Add a new checkpoint to an existing milestone') and distinguishes it from sibling tools like 'create_checkpoint' (which doesn't exist) or 'update_checkpoint'. It specifies the resource being modified (checkpoint within a milestone) and the operation (addition with optional positioning).

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 description implies usage when adding checkpoints to milestones, but provides no explicit guidance on when to use this versus alternatives like 'update_checkpoint' or 'complete_checkpoint'. It mentions optional positioning but doesn't clarify prerequisites or constraints beyond what's in the parameter documentation.

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