Skip to main content
Glama

ppm_milestone_start

Start a milestone by moving it from planned to in progress, enabling work to begin.

Instructions

Transition a milestone from 'planned' to 'in_progress'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
milestone_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `ppm_milestone_start` tool handler. Decorated with @mcp.tool(), it calls `ppm.milestone` Odoo model action 'action_start' with the given milestone_id, then returns the updated milestone record fields (name, state, date_planned, date_actual, project_id).
    @mcp.tool()
    def ppm_milestone_start(milestone_id: int) -> dict[str, Any]:
        """Transition a milestone from 'planned' to 'in_progress'."""
        client().call_action("ppm.milestone", "action_start", [milestone_id])
        return _read_state("ppm.milestone", milestone_id, _MILESTONE_FIELDS)
  • Constant `_MILESTONE_FIELDS` defining the fields fetched after the milestone action: name, state, date_planned, date_actual, project_id.
    _MILESTONE_FIELDS = ["name", "state", "date_planned", "date_actual", "project_id"]
  • Helper `_read_state` used to read and return the milestone record after the action is performed.
    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]
  • Registration via `@mcp.tool()` decorator on line 44 which registers the function as an MCP tool.
    @mcp.tool()
  • Helper `client()` function that creates/reuses the OdooClient instance used to call Odoo server actions.
    def client() -> OdooClient:
        global _client
        if _client is None:
            _client = OdooClient.from_env()
        return _client
Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits such as permissions, side effects, reversibility, or error conditions, leaving a significant gap for a mutation tool.

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?

Single sentence, 8 words, no redundancy. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple but lacks parameter details and usage context. Output schema exists but is not described. Adequate but could be improved with more behavioral and parameter information.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the 'milestone_id' parameter beyond its name. No constraints or format details are given, which the description should compensate for.

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?

Description clearly states the action (transition) and the state change from 'planned' to 'in_progress', aligning with the tool name. It distinguishes from siblings like ppm_milestone_achieve or ppm_milestone_cancel.

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?

No explicit guidance on when to use this tool versus alternatives like ppm_milestone_achieve or ppm_milestone_cancel. Usage is implied but not clarified.

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