Skip to main content
Glama

Coline

Add or change a milestone

save_milestone

Adds a milestone to a project (without milestoneId) or changes one.

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": {
      "workspace": "<workspace>",
      "projectId": "<projectId>"
    },
    "name": "save_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
projectIdYes
sortOrderNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
targetDateNo
milestoneIdNo

Output Schema

NameRequiredDescriptionDefault
milestoneYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, and the description adds the useful dispatch rule that milestoneId toggles create vs update. It stops short of saying what happens to unspecified fields on an update (full replace vs partial merge), what an update returns, or what errors occur for an invalid projectId.

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?

One short sentence with no filler, and the operative condition is front-loaded in parentheses right after the verb. It is efficient rather than padded, though it is close to the minimum and the parenthetical reads slightly like a schema note rather than guidance.

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?

For a six-parameter mutation tool with 17% schema coverage, a single clause is thin. An output schema exists so return values need not be explained, but partial-update semantics, validation behavior, and the roles of the undocumented parameters are all missing.

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 only 17% of six parameters, so the description must compensate. It does explain the meaning of milestoneId's presence, which is the single most consequential parameter, but name, targetDate, and sortOrder remain undocumented in both places, leaving the gaps unaddressed.

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 ("Adds a milestone to a project") and delimits two modes: creation when milestoneId is absent, modification otherwise. It does not name any sibling tool, but the create-vs-change distinction is explicit enough to separate it from adjacent save_* 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 condition selecting create versus update is stated via milestoneId presence, which is genuinely actionable. However, there is no guidance on prerequisites (permissions, whether the project must exist) and no direction on when to prefer this over any alternative path for editing project structure.

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