Skip to main content
Glama

Create project milestone

create_project_milestone

Create a new project milestone. Requires project_milestones:write scope.

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": {
      "project_id": "<project_id>",
      "name": "<name>",
      "due_date": "<due_date>"
    },
    "name": "create_project_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesMilestone name (required)
statusNoMilestone status
due_dateYesDue date (ISO 8601, required)
phase_idNoPhase the milestone belongs to - resolve via list_project_phases
project_idYesProject ID (required) - resolve via list_projects
descriptionNoDescription
is_criticalNoWhether the milestone is on the critical path
completed_dateNoCompleted date (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / phase_id / description
      Previous value: -"Phase the milestone belongs to"New value: +"Phase the milestone belongs to - resolve via list_project_phases"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID (required)"New value: +"Project ID (required) - resolve via list_projects"
  2. Changed2 schema fields changed
    • addedInput schema / properties / is_critical
      Added value: +{
      +  "description": "Whether the milestone is on the critical path",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / phase_id
      Added value: +{
      +  "description": "Phase the milestone belongs to",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  4. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  5. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  6. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so the safety profile is known. The description adds the auth scope requirement, which is genuinely useful context not in the annotations, but says nothing about duplicate-name behavior, side effects, or whether referenced phase/project must exist.

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?

Two short sentences, front-loaded with purpose then prerequisite. Nothing is wasted, though the extreme brevity leaves gaps that other dimensions penalize.

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?

For a mutation tool with no output schema, the description covers creation and auth but not the return value or failure modes (nonexistent project/phase, duplicate names). The fully documented schema compensates for the parameter side, keeping this at a minimum-viable level.

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 description coverage is 100% and parameters carry their own docs (including resolve hints via list_projects and list_project_phases). The description adds no parameter information, so the baseline 3 applies.

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?

States a specific verb and resource ('Create a new project milestone'), which is unambiguous against the many create_* siblings. It does not, however, distinguish itself from closely related siblings such as create_project_phase or create_project_task.

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?

The only guidance is the required scope. Nothing says when to create a milestone versus a phase or task, or when to use update_project_milestone instead. No prerequisites or exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources