Skip to main content
Glama

create-milestone

Create a milestone for a project or phase. Required: name and project ID. Optionally specify phase, dates, status, priority, completion, color, reminder, and notes.

Instructions

Create a new milestone for a project or phase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesMilestone name
project_idYesProject ID
phase_idNoPhase ID (optional)
descriptionNoMilestone description
dateNoMilestone date (YYYY-MM-DD format)
start_dateNoMilestone start date (YYYY-MM-DD format)
end_dateNoMilestone end date (YYYY-MM-DD format)
statusNoMilestone status (numeric)
priorityNoPriority level (1-5, where 1 is highest)
completedNoCompletion status (0=not completed, 1=completed)
completed_dateNoCompletion date (YYYY-MM-DD format)
notesNoAdditional notes
colorNoMilestone color (hex color code)
reminder_dateNoReminder date (YYYY-MM-DD format)
activeNoActive status (1=active, 0=archived)
Behavior2/5

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

No annotations provided; description only says 'Create a new milestone', implying creation but omitting behavioral details like side effects, idempotency, permissions, or response format. With no annotations, description fails to disclose critical traits.

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?

Single sentence is concise and front-loaded. However, it could benefit from additional context without being verbose. Efficient but minimal.

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

Completeness2/5

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

High complexity (15 params, no output schema, no annotations) requires richer description. Lacks explanation of milestone semantics, typical usage, validation rules, or return value. Incomplete for effective agent invocation.

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?

Input schema has 15 parameters with full descriptions (100% coverage). Description adds no additional meaning beyond what schema already provides. Baseline 3 is appropriate as no extra value from description.

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?

Description clearly states verb 'Create' and resource 'milestone', with context 'for a project or phase'. Effectively distinguishes from siblings like update-milestone or delete-milestone.

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?

No guidance on when to use this tool vs alternatives. Does not specify prerequisites, context, or when not to use it. Sibling tools include many create and milestone-related operations, but no differentiation provided.

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/asachs01/float-mcp'

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