Skip to main content
Glama

ppm_milestone_achieve

Mark a milestone as achieved and record the current date as the actual completion date.

Instructions

Mark a milestone as achieved; records today as the actual date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
milestone_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the ppm_milestone_achieve MCP tool. It takes a milestone_id integer, calls the Odoo server action 'action_achieve' on 'ppm.milestone' via the OdooClient, and returns the updated milestone state fields (name, state, date_planned, date_actual, project_id).
    @mcp.tool()
    def ppm_milestone_achieve(milestone_id: int) -> dict[str, Any]:
        """Mark a milestone as achieved; records today as the actual date."""
        client().call_action("ppm.milestone", "action_achieve", [milestone_id])
        return _read_state("ppm.milestone", milestone_id, _MILESTONE_FIELDS)
  • The constant _MILESTONE_FIELDS defining the fields read back after a milestone state transition: name, state, date_planned, date_actual, project_id.
    _MILESTONE_FIELDS = ["name", "state", "date_planned", "date_actual", "project_id"]
  • The @mcp.tool() decorator on line 44 (for ppm_milestone_start) shows the registration pattern; the same decorator is used on line 51 for ppm_milestone_achieve.
    @mcp.tool()
  • The OdooClient.call_action helper method used by ppm_milestone_achieve to invoke the 'action_achieve' server method on the Odoo model 'ppm.milestone'.
    def call_action(self, model: str, method: str, ids: list[int]) -> Any:
        """Invoke an `action_*` button method on the given record ids."""
        return self.execute_kw(model, method, [ids])
  • The OdooClient.read helper method used by _read_state to retrieve the updated milestone fields after the action.
    def read(
        self,
        model: str,
        ids: list[int],
        fields: list[str] | None = None,
    ) -> list[dict[str, Any]]:
        kwargs = {"fields": fields} if fields else {}
        return self.execute_kw(model, "read", [ids], kwargs)
Behavior2/5

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

With no annotations provided, the description must fully disclose behavior. It mentions setting the actual date to today but omits side effects (e.g., notifications), reversibility, or required permissions for this mutation.

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 a single sentence with no irrelevant words. It is concise but could benefit from additional structure (e.g., separate lines for purpose and details).

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 lack of annotations and minimal parameter description, the tool description is incomplete. An output schema exists but is not referenced, and prerequisites or conditions for achieving a milestone are absent.

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?

The only parameter, milestone_id, is not explained beyond its schema title. The description adds no context about how to obtain or use this ID. With 0% schema description coverage, the description should compensate but does not.

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 action ('Mark a milestone as achieved') and the resource ('milestone'). It adds a specific behavioral detail ('records today as the actual date') that distinguishes it from sibling tools like ppm_milestone_start 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives such as ppm_milestone_start, ppm_milestone_cancel, or ppm_milestone_miss. The agent must infer context from the tool name alone.

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