Skip to main content
Glama
Sign In

AimYear

by io.github.Yahhi
OverviewDiscussionsAdmin

Edit milestone

edit_milestone
Idempotent

Change one milestone: title, kind (count or steps), metric, target, due date, status or track. status=retired drops it without finishing; done or retired moves its track to the next milestone. Its steps are kept.

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": "edit_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoYYYY-MM-DD in the user's timezone
kindNocount: progress is a recorded value against target ("talk to 20 people"); steps: progress is steps done ("implement the onboarding flow"), no metric needed. Default: count when metric and target are given, else steps; an existing milestone keeps its kind
titleNo
metricNo
statusNo
targetNo
trackIdNomove it to this track (set_tracks)
milestoneIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / trackId
      Added value: +{
+  "description": "move it to this track (set_tracks)",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "count: progress is a recorded value against target (\"talk to 20 people\"); steps: progress is steps done (\"implement the onboarding flow\"), no metric needed. Default: count when metric and target are given, else steps; an existing milestone keeps its kind",
+  "enum": [
+    "count",
+    "steps"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (which only cover idempotency and non-destructiveness) by disclosing real side effects: status=retired drops the milestone without finishing, and done/retired advances its track to the next milestone. It also reassures that steps are preserved, which an agent would otherwise have to guess.

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 dense sentences, front-loaded with the scope and followed by the highest-value behavioral caveats. No filler and no restatement of the title.

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 non-readonly mutation with no output schema, the description covers the state transitions an agent most needs to avoid surprises. It does not say what the response contains or whether partial updates are returned, a minor omission given annotations carry the safety profile.

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

Parameters4/5

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

Schema coverage is only 38%, so the description must compensate, and it does by enumerating every editable field (title, kind, metric, target, due, status, track) and adding the status=retired semantics the schema lacks. Gaps remain around target/metric interaction, which the schema's kind note only partially covers.

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 ('Change') and resource ('one milestone') and enumerates the editable fields, so it reads clearly against the plural sibling set_milestones. It never names that sibling explicitly, so sibling differentiation is implied rather than stated.

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 single-milestone framing implies this edits an existing milestone rather than creating one, and the status notes hint at lifecycle usage. However, there is no explicit 'use this instead of set_milestones when...' guidance or statement of prerequisites, so selection between siblings is left to inference.

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

All AimYear toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources