Skip to main content
Glama

ppm_risk_reopen

Reopen a closed risk to return it to the 'identified' status for further assessment.

Instructions

Reopen a closed risk back to 'identified'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
risk_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool handler that reopens a closed risk by calling the Odoo 'action_reopen' server action on ppm.risk, then reads back the updated state fields.
    @mcp.tool()
    def ppm_risk_reopen(risk_id: int) -> dict[str, Any]:
        """Reopen a closed risk back to 'identified'."""
        client().call_action("ppm.risk", "action_reopen", [risk_id])
        return _read_state("ppm.risk", risk_id, _RISK_FIELDS)
  • Schema definition of the fields returned by ppm_risk_reopen (and other risk tools).
    _RISK_FIELDS = [
        "name",
        "state",
        "risk_type",
        "probability",
        "impact",
        "risk_score",
        "risk_level",
        "project_id",
        "owner_id",
    ]
  • Registration of ppm_risk_reopen as an MCP tool via the @mcp.tool() decorator on FastMCP instance.
    @mcp.tool()
  • Helper function providing the OdooClient singleton used by ppm_risk_reopen.
    def client() -> OdooClient:
        global _client
        if _client is None:
            _client = OdooClient.from_env()
        return _client
  • Helper function that reads and returns the record state 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]
Behavior2/5

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

No annotations exist, so the description should fully disclose behaviors. It only states the state change, missing details like permission requirements, side effects, or whether the risk must be closed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is very short but lacks important details, making it under-specifying rather than concise. It earns its place by stating purpose, but could be more informative without excess.

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?

For a simple tool with one parameter and an output schema, the description should cover state prerequisites and potential errors. It is too minimal given no annotations.

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 description coverage, the description should clarify the parameter. It only names risk_id, adding no extra meaning about its role or format. For a single required parameter, more context is needed.

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' and the target state 'identified', distinguishing it from sibling tools like ppm_risk_close. It is specific and unambiguous.

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 guidance is provided on when to use this tool (e.g., when a risk is closed) or alternatives. Among many risk siblings, explicit exclusions or prerequisites would help.

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