Skip to main content
Glama
Sign In
codebugs

codebugs

by faxik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

milestone_update

Update a milestone's mutable fields—description, target date, or state—while keeping its ID and kind unchanged.

Instructions

Update mutable fields of a milestone. id and kind are immutable.

Args:

  • id: Milestone slug.

  • description: New description (or None to skip).

  • target_date: New ISO target date (or None to skip).

  • state: New state (open / closing / shipped / archived).

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": {
      "id": "<id>"
    },
    "name": "milestone_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
stateNo
descriptionNo
target_dateNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses partial-update semantics ('or None to skip') and immutable fields, but does not disclose side effects such as state-transition rules, whether updates are reflected elsewhere, or failure behavior.

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?

The description is compact and front-loaded, with a one-line purpose followed by a clean Args list. Every sentence adds information; there is no filler.

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 4-parameter update tool with an output schema, the description covers the essential semantics and constraints. It only lacks explicit routing relative to sibling milestone state/status tools, which would make it fully complete.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully compensates: it defines id as a milestone slug, target_date as an ISO date, state as an enumerated set, and clarifies that None means skip rather than clear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource, 'Update mutable fields of a milestone', and explicitly states what is out of scope ('id and kind are immutable'), which helps distinguish it from milestone_create or other milestone operations.

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 usage is implied rather than contrasted with alternatives: it is for changing milestone mutable fields, and the immutability note adds a constraint. However, it does not say when to choose this over closely related siblings like milestone_set_status or milestone_close.

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

Deploy Server

Other Tools