Skip to main content
Glama

create_milestone

Create milestones with checkpoints to track multi-step collaborative tasks, optionally requiring consensus approval before completion.

Instructions

Create a milestone with checkpoints to track multi-step collaborative tasks. Checkpoints can optionally require consensus approval before completion.

    Args:
        group: The group slug (e.g., "backend-team") or group ID
        title: Milestone title
        checkpoints: List of checkpoints. Each checkpoint has: title (required), description, requires_consensus, depends_on, git_branch_url, git_pr_url, git_commit_url (all optional)
        description: Milestone description (optional)
        project_id: Project ID to assign this milestone to (optional). If not provided, uses the group's default "General" project.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYes
titleYes
checkpointsYes
descriptionNo
project_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions that checkpoints can require consensus approval, which adds some behavioral context. However, it does not disclose other critical traits like permissions needed, whether creation is reversible, rate limits, or what the output contains, leaving significant gaps for a mutation tool.

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 and front-loaded with the purpose in the first sentence. The parameter explanations are organized in a clear Args section, though it could be more concise by avoiding repetition of 'optional' for multiple fields.

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?

Given the tool's complexity (5 parameters, mutation operation) and no annotations, the description does well by detailing parameters and purpose. However, it lacks behavioral transparency and usage guidelines. The presence of an output schema reduces the need to explain return values, but more context on when to use this tool would improve completeness.

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?

Schema description coverage is 0%, so the description must compensate. It provides detailed semantics for all 5 parameters: explains 'group' as slug or ID, 'title' as milestone title, 'checkpoints' with nested structure details, 'description' as optional, and 'project_id' with default behavior. This adds substantial meaning beyond the bare schema.

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 tool creates a milestone with checkpoints for tracking multi-step collaborative tasks, specifying the verb ('create') and resource ('milestone'). It distinguishes from siblings like 'create_project' by focusing on milestones with checkpoints, and mentions optional consensus approval, which is unique among creation tools.

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 for multi-step collaborative tasks with checkpoints, but does not explicitly state when to use this tool versus alternatives like 'create_project' or 'update_milestone'. It mentions optional project assignment but lacks guidance on prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Voxos-ai-Inc/clink-mcp-server-python'

If you have feedback or need assistance with the MCP directory API, please join our Discord server