Skip to main content
Glama

ppm_issue_start

Transition an issue to 'in_progress' to begin active work on it.

Instructions

Move an issue to 'in_progress'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the ppm_issue_start tool. It calls the 'action_issue_start' button method on the 'ppm.risk' model via the Odoo client, then reads back and returns the issue state.
    @mcp.tool()
    def ppm_issue_start(issue_id: int) -> dict[str, Any]:
        """Move an issue to 'in_progress'."""
        client().call_action("ppm.risk", "action_issue_start", [issue_id])
        return _read_state("ppm.risk", issue_id, _ISSUE_FIELDS)
  • The function signature defines the schema: takes an integer 'issue_id' and returns a dict. The returned fields correspond to _ISSUE_FIELDS (name, state, issue_state, project_id, owner_id, date_resolved).
    @mcp.tool()
    def ppm_issue_start(issue_id: int) -> dict[str, Any]:
        """Move an issue to 'in_progress'."""
        client().call_action("ppm.risk", "action_issue_start", [issue_id])
        return _read_state("ppm.risk", issue_id, _ISSUE_FIELDS)
  • The @mcp.tool() decorator on line 292 registers ppm_issue_start as an MCP tool.
    @mcp.tool()
    def ppm_issue_start(issue_id: int) -> dict[str, Any]:
  • The _read_state helper used by ppm_issue_start to fetch the record state after the action.
        report_id = rows[0]["id"]
    return _read_state(
        "ppm.status.report",
  • The call_action method on OdooClient, which is used by ppm_issue_start to invoke the Odoo server action.
    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?

Without annotations, the description must disclose behavioral traits. It only states the action but omits side effects, required prior state, or potential failures. This is insufficient for a mutation tool.

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?

The description is a single, efficient sentence. Every word contributes to the purpose, and there is no fluff.

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

Completeness3/5

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

Given the tool's simplicity (one param, output schema present), the description is minimally adequate. However, it lacks context about preconditions or the meaning of 'in_progress', leaving gaps for completeness.

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?

The schema has one parameter (issue_id) with no description, and the tool description adds no extra meaning. With 0% schema description coverage, the description should clarify the parameter's role, but it does not.

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 that the tool moves an issue to the 'in_progress' state. This distinguishes it from sibling tools like ppm_issue_resolve or ppm_issue_assign, which handle different transitions.

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 versus alternatives such as ppm_issue_assign or ppm_issue_escalate. There is no mention of prerequisites or conditions for calling it.

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