Skip to main content
Glama

ppm_risk_start_mitigation

Transition a risk to the 'mitigating' status to start the mitigation process.

Instructions

Transition a risk to 'mitigating'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
risk_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for ppm_risk_start_mitigation tool. Takes a risk_id, calls the Odoo server action 'action_start_mitigation' on 'ppm.risk' model to transition the risk to 'mitigating' state, then returns the updated risk with standard risk fields.
    @mcp.tool()
    def ppm_risk_start_mitigation(risk_id: int) -> dict[str, Any]:
        """Transition a risk to 'mitigating'."""
        client().call_action("ppm.risk", "action_start_mitigation", [risk_id])
        return _read_state("ppm.risk", risk_id, _RISK_FIELDS)
  • Registration via @mcp.tool() decorator on line 226 registers the function as an MCP tool named 'ppm_risk_start_mitigation'.
    @mcp.tool()
  • Schema definition for risk fields used by the tool to read back state after the action.
    _RISK_FIELDS = [
        "name",
        "state",
        "risk_type",
        "probability",
        "impact",
        "risk_score",
        "risk_level",
        "project_id",
        "owner_id",
    ]
  • Helper function _read_state used by ppm_risk_start_mitigation to read the risk record after the action call.
    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 behavioral traits such as required previous state, side effects, or whether the transition is reversible. For a state-changing tool, this is a significant omission.

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 sentence that gets straight to the point. It is appropriately sized for a simple operation, though it could benefit from a bit more context without becoming verbose.

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?

The tool is simple, but the description omits crucial context: what 'mitigating' means, what the output schema contains, and any prerequisites. Given the lack of annotations, the description alone is insufficient for complete understanding.

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 input schema has 0% description coverage, and the description does not mention the risk_id parameter or its meaning. The agent gains no additional context beyond the parameter name, which is minimal.

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 'Transition a risk to 'mitigating'' clearly states a specific verb and resource, and it is distinct from sibling tools like ppm_risk_start_analysis. However, it could be more explicit about the exact state change (e.g., 'changes risk status to Mitigating').

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?

The description provides no guidance on when to use this tool versus alternatives like ppm_risk_start_analysis or ppm_risk_start_monitoring. No conditions, prerequisites, or exclusions are mentioned, leaving the agent to infer usage from the name alone.

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