Skip to main content
Glama
Sign In
codebugs

codebugs

by faxik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

milestone_create

Create a milestone to track a release or ongoing stream. Specify kind, description, and optional target date for releases.

Instructions

Create a new milestone.

Args:

  • id: Slug identifier, e.g. 'release/1.2' or 'stream/security'.

  • kind: 'release' or 'stream'. Streams never close.

  • description: Short charter for the milestone.

  • target_date: ISO date (e.g. '2026-06-30'). Optional, releases only.

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": {
      "id": "<id>",
      "kind": "<kind>",
      "description": "<description>"
    },
    "name": "milestone_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindYes
descriptionYes
target_dateNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are present, so the description carries the disclosure burden. It does add meaningful behavioral context: streams never close, and target_date is optional and releases-only. It stops short of describing duplicate-ID behavior or other failure modes, but the side effect of creation is clear.

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?

The description is a one-sentence purpose followed by a compact, front-loaded Args list. Every line earns its place with examples, allowed values, or constraints. There is no padding or repetition of the schema.

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?

For a four-parameter creation tool with an output schema, the description defines every argument with examples and constraints, so an agent can construct a valid call. It lacks routing guidance and some edge-case behavior, but the core invocation context is well covered.

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%, and the description fully compensates. It explains id with concrete slug examples, constrains kind to 'release' or 'stream', describes description as a charter, and provides ISO format plus release-only semantics for target_date. This is far richer than the bare schema fields.

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 opens with a specific verb and resource: 'Create a new milestone.' The word 'new' clearly distinguishes this from mutation-focused siblings such as milestone_update, milestone_close, and milestone_defer. No ambiguity about what the tool does.

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 guidance about when to use milestone_create versus alternatives like milestone_update, milestone_add_item, or milestone_close. The only rule provided, 'Streams never close,' is a domain constraint, not a routing instruction.

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