Skip to main content
Glama

ppm_milestone_miss

Mark a milestone as missed to update its status and trigger related workflow actions.

Instructions

Mark a milestone as missed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
milestone_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the ppm_milestone_miss tool. Calls action_miss on the ppm.milestone model via the Odoo client, then returns the updated record state.
    @mcp.tool()
    def ppm_milestone_miss(milestone_id: int) -> dict[str, Any]:
        """Mark a milestone as missed."""
        client().call_action("ppm.milestone", "action_miss", [milestone_id])
        return _read_state("ppm.milestone", milestone_id, _MILESTONE_FIELDS)
  • Registration of ppm_milestone_miss as an MCP tool via the @mcp.tool() decorator on the FastMCP instance.
    @mcp.tool()
    def ppm_milestone_miss(milestone_id: int) -> dict[str, Any]:
  • Helper function _read_state used by ppm_milestone_miss to fetch and return the updated milestone record after the 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]
  • OdooClient.call_action — the low-level helper that invokes action_miss on the ppm.milestone model via JSON-RPC execute_kw.
    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])
  • Schema fields returned by the ppm_milestone_miss tool — the list of Odoo fields read from the milestone after the action.
    _MILESTONE_FIELDS = ["name", "state", "date_planned", "date_actual", "project_id"]
Behavior2/5

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

With no annotations, the description carries full burden but only states the action. It fails to disclose any behavioral traits such as side effects, required prior states, or whether the operation is reversible. Minimal transparency.

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?

Extremely concise at one sentence, which is efficient but sacrifices completeness. Could be restructured to front-load key behavioral info.

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 existence of an output schema and sibling tools, the description is incomplete. Lacks context on workflow integration, state prerequisites, and relationship to other milestone actions.

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 input schema has 0% description coverage for the single parameter 'milestone_id'. The description adds no meaning beyond the schema—it does not explain what milestone_id represents or how to obtain it.

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 clearly states the action ('mark') and resource ('milestone') and the resulting status ('missed'). It distinguishes from sibling tools like ppm_milestone_achieve or ppm_milestone_cancel by specifying the outcome.

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 usage guidelines provided. The description does not indicate when to use this tool versus alternatives such as ppm_milestone_achieve or ppm_milestone_reopen. There is no mention of prerequisites or context.

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