Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_milestone

Add a milestone to a completion path to track progress with status options: pending, in_progress, completed, or blocked.

Instructions

Add milestone to completion path

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": {
      "completion_path_id": "<completion_path_id>",
      "name": "<name>",
      "status": "<status>"
    },
    "name": "add_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
completion_path_idYesCompletion path ID this milestone belongs to
nameYesMilestone name
statusYes'pending', 'in_progress', 'completed', 'blocked'pending
descriptionNoMilestone description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

B3/5.0
Behavior2/5

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

Annotations already indicate the tool is not read-only and not destructive. The description adds no extra behavioral context such as side effects, permission requirements, or the need for the completion path to exist. Minimal transparency beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise. However, it is too short and lacks useful structure or elaboration, making it merely adequate rather than exemplary.

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?

Given the tool has 4 parameters, no output schema, and many sibling tools, the description is too minimal. It does not explain what a milestone is, any constraints, or what the tool returns. More context is needed for effective use.

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 100%, so the schema already documents all parameters. The description ('Add milestone to completion path') does not add any meaning beyond the parameter names and descriptions. Baseline score of 3 is appropriate.

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 clearly states the verb 'Add' and the resource 'milestone' with context 'to completion path'. It distinguishes well from sibling tools like add_task or add_subtask which target different entities.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., update_milestone, delete_milestone, get_milestones_by_path). It does not mention prerequisites or typical use cases.

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