Skip to main content
Glama

ppm_change_request_reject

Reject a change request by providing a mandatory reason. Initiates the reject wizard to process the rejection.

Instructions

Reject a Change Request with a required reason (runs the reject wizard).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cr_idYes
reasonYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for ppm_change_request_reject. It creates a reject wizard record with the given reason, confirms the rejection via action_confirm_reject, and returns the updated Change Request state.
    @mcp.tool()
    def ppm_change_request_reject(cr_id: int, reason: str) -> dict[str, Any]:
        """Reject a Change Request with a required reason (runs the reject wizard)."""
        wizard_id = client().execute_kw(
            "ppm.change.request.reject.wizard",
            "create",
            [{"change_request_id": cr_id, "reason": reason}],
        )
        client().call_action("ppm.change.request.reject.wizard", "action_confirm_reject", [wizard_id])
        return _read_state("ppm.change.request", cr_id, _CR_FIELDS)
  • The schema fields read from the change request after rejection (name, state, project_id, change_type, priority, initiator_id).
    _CR_FIELDS = ["name", "state", "project_id", "change_type", "priority", "initiator_id"]
  • Registration of the tool via the @mcp.tool() decorator on the ppm_change_request_reject function.
    @mcp.tool()
Behavior2/5

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

Mentions 'runs the reject wizard' but does not disclose side effects, required permissions, or what the wizard entails; no annotations to supplement.

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?

Single sentence, front-loaded with action and key detail, but could be slightly more informative without losing conciseness.

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?

Lacks details on output or behavior despite having 2 parameters and an output schema; insufficient for a mutating tool with potential side effects.

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?

With 0% schema coverage, the description only repeats that reason is required, as already in the schema, and offers no explanation of cr_id or their formats.

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 (Reject), the resource (Change Request), and a key detail (required reason), effectively distinguishing it from siblings like approve or 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 usage for rejection but provides no explicit guidance on when to use versus alternatives, nor any contraindications.

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