Skip to main content
Glama

Tick a milestone

tick_milestone

Mark a milestone as done or undone to keep goal progress accurate and track completed steps in your Life Compass plan.

Instructions

Mark a milestone done (or undone).

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

Input Schema

NameRequiredDescriptionDefault
doneNo
milestoneIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It implies a state mutation but says nothing about whether the change is idempotent, what happens if milestoneId is unknown, whether completing a milestone affects plan progress or status, or what is returned.

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 short sentence, front-loaded with the action and with no wasted wording. Its brevity borders on under-specification rather than verbosity, which is a completeness issue rather than a structural one.

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 mutation tool with no annotations, no output schema, and 0% parameter documentation, the description should do more. It omits where the milestoneId comes from, whether the toggle is reversible/safe to repeat, and what a caller should expect afterward.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain both parameters. It loosely maps 'done (or undone)' to the done boolean, but gives no meaning for milestoneId — not its source (get_plan, save_milestones), format, or uniqueness — and never states that done defaults to true.

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 pairs a specific verb (mark done/undone) with a specific resource (a milestone), so the operation is immediately legible. It does not explicitly distinguish itself from the closely named sibling save_milestones, leaving the agent to infer that this toggles status rather than creating or editing milestone definitions.

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?

There is no guidance on when to call this versus save_milestones or get_plan, and no prerequisites such as requiring the milestone to already exist. The only usage signal is the parenthetical '(or undone)', which hints at reversibility but not context.

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