Skip to main content
Glama

ppm_milestone_cancel

Cancel a milestone by providing its unique ID. This tool triggers the workflow action to stop the milestone's progress.

Instructions

Cancel a milestone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
milestone_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler that cancels a milestone by calling the Odoo action_cancel method on ppm.milestone, then reads back the updated state.
    @mcp.tool()
    def ppm_milestone_cancel(milestone_id: int) -> dict[str, Any]:
        """Cancel a milestone."""
        client().call_action("ppm.milestone", "action_cancel", [milestone_id])
        return _read_state("ppm.milestone", milestone_id, _MILESTONE_FIELDS)
  • Schema/fields definition used to read milestone state after the cancel action.
    _MILESTONE_FIELDS = ["name", "state", "date_planned", "date_actual", "project_id"]
  • The @mcp.tool() decorator registers this function as an MCP tool named ppm_milestone_cancel.
    @mcp.tool()
    def ppm_milestone_cancel(milestone_id: int) -> dict[str, Any]:
  • Helper function that returns the singleton OdooClient instance used by the handler.
    def client() -> OdooClient:
        global _client
        if _client is None:
            _client = OdooClient.from_env()
        return _client
  • Helper that reads and returns the record's current state after the cancel action.
    def _read_state(model: str, rec_id: int, fields: list[str]) -> dict[str, Any]:
        rows = client().read(model, [rec_id], fields)
        if not rows:
            raise ValueError(f"{model} id={rec_id} not found")
        return rows[0]
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. Only 'Cancel a milestone' is given, lacking details on effects (e.g., irreversibility, permission requirements, status changes).

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 short sentence, which is concise but too brief. It could include more context without being verbose.

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?

Despite having only one parameter and no annotations, the description does not explain return values or side effects. Given the existence of output schema and sibling tools, more context is needed for an agent to use this tool effectively.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning to the single parameter 'milestone_id'. The parameter's purpose is not explained beyond its name.

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 'Cancel a milestone' clearly states the verb (cancel) and resource (milestone). It distinguishes from sibling tools like ppm_milestone_achieve or ppm_milestone_start, but could specify what cancel entails.

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 on when to use this tool instead of other milestone actions (e.g., achieve, miss, reopen). No exclusions or prerequisites provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wethti/qod-ppm-odoo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server