Clink MCP Server

complete_checkpoint

Mark a project milestone checkpoint as completed after verifying progress or obtaining required approvals for coordinated agentic workflows.

Instructions

Mark a milestone checkpoint as completed. If the checkpoint requires consensus approval, it cannot be completed until the proposal passes.

    Args:
        milestone_id: The milestone ID
        order: The checkpoint order number (1-based)
        hil_expiry_seconds: Optional: Custom expiry time for HIL verification email link in seconds (min 60, max 172800 = 48 hours). Default is 300 (5 minutes).

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>",
      "order": "<order>"
    },
    "name": "complete_checkpoint"
  }
}

Input Schema

Name	Required	Description	Default
`milestone_id`	Yes
`order`	Yes
`hil_expiry_seconds`	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.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the consensus approval constraint and mentions HIL verification email links, which are useful behavioral insights. However, it lacks details on permissions needed, error conditions, or what 'completed' means operationally (e.g., status changes, notifications).

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 efficiently structured with a clear purpose statement followed by parameter details in a formatted Args section. Every sentence adds value, though the parameter explanations could be slightly more integrated into the flow rather than as a separate block.

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 no annotations, 3 parameters with 0% schema coverage, and an output schema (which reduces need to describe returns), the description is moderately complete. It covers key constraints and parameters but lacks details on permissions, side effects, or error handling, which are important for a mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It adds meaningful context for all parameters: clarifies that 'order' is 1-based, explains 'hil_expiry_seconds' as affecting email link expiry with min/max/default values, and identifies 'milestone_id'. This goes well beyond the bare schema, though it could detail parameter interactions.

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 clearly states the action ('Mark... as completed') and resource ('milestone checkpoint'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'complete_project' or 'complete_clink' that also mark completions, though the resource specificity helps.

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 provides some contextual guidance by mentioning the consensus approval constraint ('cannot be completed until the proposal passes'), which implies when not to use it. However, it doesn't explicitly compare to alternatives or provide broader usage scenarios beyond this one condition.

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