Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_milestone

Destructive

Delete a milestone after validating associated tasks. Requires milestone ID and deletion reason with severity and source.

Instructions

Delete milestone with task validation

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>",
      "note_reason": "<note_reason>",
      "note_severity": "<note_severity>",
      "note_source": "<note_source>",
      "note_type": "<note_type>"
    },
    "name": "delete_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMilestone ID
note_reasonYesDeletion reason
note_severityYes'info', 'warning', 'error'
note_sourceYes'ai' or 'user'
note_typeYes'entry_deletion'entry_deletion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true, so the agent knows it's destructive. The phrase 'with task validation' adds some behavioral context (likely checking for tasks before deletion) but does not clarify what happens if validation fails or if tasks are deleted. No contradiction with annotations.

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?

The description is extremely concise with just a few words, no unnecessary content. However, it sacrifices some clarity for brevity.

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?

The tool is destructive with 5 required parameters, but the description does not explain return behavior, error messages, or the full implications of 'task validation'. No output schema exists, so the description should provide more completeness.

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%, meaning all five parameters have descriptions in the input schema. The tool description does not add any additional meaning beyond what the schema provides, such as how parameters relate to task validation. Baseline 3 applies.

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 'Delete milestone with task validation' clearly states the action (delete) and resource (milestone). It hints at a validation process, distinguishing it from other delete tools, but does not explicitly differentiate from siblings like delete_task.

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?

No guidance is provided on when to use this tool versus alternatives such as delete_task or delete_sidequest. The description implies usage for milestone deletion but lacks any context about prerequisites or exclusions.

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