Skip to main content
Glama

ppm_change_request_reset_draft

Reset a submitted or rejected change request to draft by providing its ID.

Instructions

Return a submitted or rejected Change Request to draft.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cr_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for ppm_change_request_reset_draft. Calls Odoo's action_reset_draft on ppm.change.request to return a submitted or rejected Change Request back to draft state, then reads and returns the current state fields.
    @mcp.tool()
    def ppm_change_request_reset_draft(cr_id: int) -> dict[str, Any]:
        """Return a submitted or rejected Change Request to draft."""
        client().call_action("ppm.change.request", "action_reset_draft", [cr_id])
        return _read_state("ppm.change.request", cr_id, _CR_FIELDS)
  • The tool is registered as an MCP tool via the @mcp.tool() decorator on the ppm_change_request_reset_draft function, using FastMCP's automatic tool registration.
    @mcp.tool()
    def ppm_change_request_reset_draft(cr_id: int) -> dict[str, Any]:
        """Return a submitted or rejected Change Request to draft."""
        client().call_action("ppm.change.request", "action_reset_draft", [cr_id])
        return _read_state("ppm.change.request", cr_id, _CR_FIELDS)
  • The _CR_FIELDS list defines the schema of fields returned by the tool (name, state, project_id, change_type, priority, initiator_id).
    _CR_FIELDS = ["name", "state", "project_id", "change_type", "priority", "initiator_id"]
  • The call_action helper method on OdooClient that invokes the Odoo server-side action method 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])
Behavior2/5

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

With no annotations provided, the description should disclose behavioral traits. It only states the action, omitting details like side effects, required states beyond mentioned, or return value.

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, concise, and front-loaded; no wasted words.

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

Completeness4/5

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

For a simple reset tool with one parameter, the description is minimally adequate. However, given the presence of an output schema and no behavioral details, a bit more completeness would be better.

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

Parameters1/5

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

The single parameter cr_id has no description in the schema (0% coverage) and the description adds no meaning about what it represents.

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 (return to draft) on a specific resource (Change Request) and specifies the applicable statuses (submitted or rejected), distinguishing it from sibling tools like approve or reject.

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 when to use (when a change request is submitted or rejected and needs to be returned to draft), but provides no explicit guidance on when not to use or alternatives.

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