Skip to main content
Glama

Save milestones

save_milestones

Set a goal's milestones as 4–8 concrete, tickable actions across quarters 1–4, replacing the list while preserving ticks for milestones with the same text.

Instructions

Set a goal's milestones: 4 to 8 concrete, tickable actions spread across quarters 1–4, most in the first two. Replaces the list; ticks are kept for milestones with the same text.

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": {
      "goalId": "<goalId>",
      "milestones": "<milestones>"
    },
    "name": "save_milestones"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalIdYes
milestonesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/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 it does disclose the critical trait that this REPLACES the existing list and that ticks survive only for milestones with identical text — key information for a mutation with destructive elements. It stops short of describing validation failures, e.g. what happens when fewer than 4 or more than 8 milestones are supplied.

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?

Two tight sentences, front-loaded with the operation and followed immediately by the replace/tick-preservation consequence. No filler and nothing buried.

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 two-parameter mutation with nested item objects, no annotations and no output schema, the description covers purpose, content rules, and replace semantics adequately. The main gaps are the count discrepancy with the schema and the absence of error behavior, which keep it from being fully complete.

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 0%, so the description must compensate, and it partially does: it explains milestone content constraints and implies 'text' is the identity key for tick preservation. But goalId is never explained, and the stated 4–8 range conflicts with the schema's minItems 1 / maxItems 10, leaving ambiguity about which constraint is enforced.

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 gives a specific verb and resource ('Set a goal's milestones') plus the shape of the payload, so the agent knows exactly what operation this performs. It does not name a sibling such as tick_milestone, though the phrase 'tickable' and 'ticks are kept' hints at the separate ticking operation without stating it.

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?

Useful content guidance is given (4–8 actions, spread across quarters 1–4, most in the first two), which tells the agent how to compose a good call. However, there is no explicit when-to-use guidance relative to alternatives like tick_milestone or add_win, and no stated preconditions such as the goal needing to exist.

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