Skip to main content
Glama

ppm_role_revoke

Revoke a role assignment by removing a user from their assigned security group. Provide the assignment ID to remove access.

Instructions

Revoke a role assignment; removes the user from the security group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assignment_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The @mcp.tool() decorated function ppm_role_revoke that implements the tool logic: calls action_revoke on ppm.role.assignment and reads back the state.
    @mcp.tool()
    def ppm_role_revoke(assignment_id: int) -> dict[str, Any]:
        """Revoke a role assignment; removes the user from the security group."""
        client().call_action("ppm.role.assignment", "action_revoke", [assignment_id])
        return _read_state("ppm.role.assignment", assignment_id, _ROLE_FIELDS)
  • The @mcp.tool() decorator registers ppm_role_revoke as an MCP tool on the FastMCP instance 'mcp'.
    @mcp.tool()
    def ppm_role_revoke(assignment_id: int) -> dict[str, Any]:
  • The _ROLE_FIELDS list defines the fields read back after the revoke action (name, state, role_id, user_id, project_id, date_from, date_to).
    _ROLE_FIELDS = ["name", "state", "role_id", "user_id", "project_id", "date_from", "date_to"]
  • The _read_state helper reads and returns the state of a record from Odoo, used by ppm_role_revoke to return the updated assignment.
    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?

With no annotations provided, the description carries full burden. It discloses the destructive nature (removes user from group) but lacks details on permissions required, reversibility, or side effects.

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 short sentence with no unnecessary words, making it highly concise.

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?

Despite low complexity (one param, no nested objects), the description omits usage context, behavioral insights, and output details. The presence of an output schema is not leveraged or mentioned.

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 schema has 0% description coverage for the single parameter 'assignment_id', and the description adds no meaning beyond the schema field name. The agent cannot infer the parameter's source or format.

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 ('Revoke a role assignment') and the effect ('removes the user from the security group'), which distinguishes it from sibling tools like ppm_role_activate.

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 use for revoking a role, but provides no explicit guidance on when to use this tool versus alternatives (e.g., when a role should be deactivated instead), nor does it specify preconditions or exclusions.

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