Skip to main content
Glama

ppm_change_request_start_review

Start the review phase for a submitted change request by specifying its ID to advance the workflow state.

Instructions

Start review of a submitted Change Request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cr_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler for ppm_change_request_start_review. Decorated with @mcp.tool(), it calls the Odoo 'action_start_review' server action on the 'ppm.change.request' model for the given record ID, then returns the updated state fields.
    @mcp.tool()
    def ppm_change_request_start_review(cr_id: int) -> dict[str, Any]:
        """Start review of a submitted Change Request."""
        client().call_action("ppm.change.request", "action_start_review", [cr_id])
        return _read_state("ppm.change.request", cr_id, _CR_FIELDS)
  • Fields schema _CR_FIELDS used to read back the change request state after the action.
    _CR_FIELDS = ["name", "state", "project_id", "change_type", "priority", "initiator_id"]
  • Registration via @mcp.tool() decorator on line 169. The FastMCP instance 'mcp' is created on line 19.
    @mcp.tool()
  • Helper method call_action on OdooClient that invokes an action_* method via 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])
    
    def close(self) -> None:
        self._http.close()
  • Helper _read_state reads record fields after the action to return updated state to the caller.
    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?

No annotations are provided, and the description does not disclose any behavioral traits beyond the action. It fails to mention side effects, authentication needs, or what happens during review.

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 concise sentence with no wasted words, though it may be too brief for some contexts.

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 tool's role in a review workflow, the description is too minimal. It lacks information on prerequisites, output, and workflow context, despite the presence of sibling tools implying a process.

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 'cr_id' parameter. Although the parameter name is somewhat self-explanatory, the lack of explicit description fails to compensate for the low coverage.

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 ('Start review') and the resource ('a submitted Change Request'), and it distinguishes from sibling tools like approve, reject, and submit.

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?

The description implies this tool is used after submission and before approval/rejection, but does not explicitly state when to use it versus alternatives or any prerequisites.

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