Skip to main content
Glama

ppm_issue_assign

Transition an issue from 'new' to 'assigned' to mark it as assigned.

Instructions

Move an issue from 'new' to 'assigned'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for ppm_issue_assign tool. Calls the 'action_issue_assign' method on the ppm.risk Odoo model to transition an issue from 'new' to 'assigned', then returns the updated state.
    @mcp.tool()
    def ppm_issue_assign(issue_id: int) -> dict[str, Any]:
        """Move an issue from 'new' to 'assigned'."""
        client().call_action("ppm.risk", "action_issue_assign", [issue_id])
        return _read_state("ppm.risk", issue_id, _ISSUE_FIELDS)
  • Fields read back after the assign action to return the updated issue state.
    _ISSUE_FIELDS = [
        "name",
        "state",
        "issue_state",
        "project_id",
        "owner_id",
        "date_resolved",
    ]
  • Registration via @mcp.tool() decorator on the FastMCP instance.
    @mcp.tool()
  • Helper method call_action on OdooClient that invokes the button method via 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])
  • Helper to read state fields after the action call, used to return the result.
    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, so the description must carry the burden. It only states 'Move an issue from new to assigned' without disclosing side effects, permissions, idempotency, or what happens if the issue is not in 'new' status. This is insufficient.

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 a single sentence, which is concise but lacks structure. It does not separate purpose from usage notes or provide any formatting. While it is not verbose, it is too brief for the information needed.

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?

Given the low complexity (1 parameter, no enums, no nested objects) and presence of an output schema, the description is incomplete. It does not explain return values, error conditions, or behavioral nuances. The description does not fully leverage available structured information.

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 one integer parameter 'issue_id' with no description. The tool description does not add any additional meaning beyond the field name. With 0% schema description coverage, the description fails to compensate.

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: moving an issue from 'new' to 'assigned'. It distinguishes from sibling tools like ppm_issue_escalate, ppm_issue_resolve, ppm_issue_start by specifying the exact state transition.

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 when an issue is in 'new' status, but it does not explicitly state prerequisites or when not to use. No alternatives are mentioned, but the sibling tool names provide some context.

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