Skip to main content
Glama

Add Milestone

add_milestone

Create a project milestone with a target completion date and associated key features to organize goals and track development progress.

Instructions

Define a milestone with a target date and associated features.

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": {
      "name": "<name>"
    },
    "name": "add_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesMilestone name (e.g. 'v1.0 Beta').
pathNoProject root directory..
featuresNoComma-separated list of key features for this milestone.
target_dateNoTarget completion date.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and delivers little: it does not say whether this persists to a project file, what happens on a duplicate milestone name (overwrite vs. error), whether it requires an initialized context, or that it mutates project state. Only the mutation implication of 'define' is conveyed.

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?

A single tight sentence with the resource front-loaded and no filler. It is arguably too terse rather than bloated, but every word earns its place.

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?

An output schema exists, so return values need not be described, and the parameter schema is fully documented. However, for a state-mutating planning tool sitting among phases, tasks, and contexts, the description omits prerequisites and side effects an agent would need before calling it.

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?

Schema coverage is 100%, so the schema already documents name, path, features, and target_date. The description restates the target date and features concepts but adds no format guidance (e.g., acceptable date formats) or relationship between 'path' and the milestone record, so it stays at the baseline.

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 states a specific verb and resource ('Define a milestone') plus the two salient attributes (target date, features), so an agent knows exactly what entity is being created. It does not differentiate from sibling list_milestones or explain how a milestone relates to phases/tasks, which keeps it below a 5.

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?

Usage is only implied: 'define' suggests creating a new planning milestone as part of project setup. There is no explicit when-to-use, no mention of when a milestone already exists, and no reference to alternatives such as list_milestones or set_phase.

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