Skip to main content
Glama

ppm_milestone_reopen

Reopen a milestone by resetting its status to 'planned'. Provide the milestone ID to restore it from a completed or cancelled state.

Instructions

Reopen a milestone back to 'planned'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
milestone_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool handler function: calls Odoo's `action_reopen` on `ppm.milestone` and returns the updated record state.
    @mcp.tool()
    def ppm_milestone_reopen(milestone_id: int) -> dict[str, Any]:
        """Reopen a milestone back to 'planned'."""
        client().call_action("ppm.milestone", "action_reopen", [milestone_id])
        return _read_state("ppm.milestone", milestone_id, _MILESTONE_FIELDS)
  • The @mcp.tool() decorator registers ppm_milestone_reopen as an MCP tool on the FastMCP server instance.
    @mcp.tool()
    def ppm_milestone_reopen(milestone_id: int) -> dict[str, Any]:
  • Helper function _read_state reads the updated record from Odoo 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]
  • Fields list used to read milestone state after the reopen action.
    _MILESTONE_FIELDS = ["name", "state", "date_planned", "date_actual", "project_id"]
  • OdooClient.call_action dispatches the server action method to the Odoo JSON-RPC API.
    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])
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'reopen' without disclosing side effects, required previous state, permissions needed, or reversibility. Minimal disclosure 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise at one sentence. No wasted words, but oversimplifies. Loses points for missing critical details that could be added without verbosity.

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 has one parameter and an output schema exists, so return values are covered. However, the description lacks behavioral context (state machine, conditions) and usage guidance. Adequate for basic understanding but incomplete for reliable invocation.

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% for milestone_id, and the description does not explain the parameter beyond naming the tool. No added meaning about what the milestone_id refers to or constraints.

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 'Reopen a milestone back to planned.' It specifies the resource (milestone) and the target state, distinguishing it from siblings like achieve, cancel, miss, and start which have different verbs and states.

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 guidelines on when to use or when not to use. No mention of prerequisites (e.g., milestone must be in a closed/cancelled state). No alternatives or exclusions provided, leaving the agent without context for selection.

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