Skip to main content
Glama

ppm_list_action_tools

List all PPM action tools and wizards exposed by this server, helping decide between custom tools and generic Odoo CRUD operations.

Instructions

List every PPM action/wizard tool this server exposes, with a one-line description.

Useful when Claude is deciding whether to call a custom tool or fall back to the generic Odoo MCP's update_record/search_records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function that implements the 'ppm_list_action_tools' tool. It uses the MCP server's list_tools() method to enumerate all registered tools and returns their names and one-line descriptions as a list of dicts.
    async def ppm_list_action_tools() -> list[dict[str, str]]:
        """List every PPM action/wizard tool this server exposes, with a one-line description.
    
        Useful when Claude is deciding whether to call a custom tool or fall back
        to the generic Odoo MCP's `update_record`/`search_records`.
        """
        registered = await mcp.list_tools()
        return [
            {"name": t.name, "summary": (t.description or "").strip().splitlines()[0]}
            for t in registered
        ]
  • The return type annotation is list[dict[str, str]], and there are no input parameters. The tool description serves as the schema documentation.
    async def ppm_list_action_tools() -> list[dict[str, str]]:
        """List every PPM action/wizard tool this server exposes, with a one-line description.
    
        Useful when Claude is deciding whether to call a custom tool or fall back
        to the generic Odoo MCP's `update_record`/`search_records`.
        """
        registered = await mcp.list_tools()
        return [
            {"name": t.name, "summary": (t.description or "").strip().splitlines()[0]}
            for t in registered
        ]
  • The tool is registered via the @mcp.tool() decorator, where 'mcp' is a FastMCP('qod-ppm') instance from the 'mcp.server.fastmcp' package (line 19).
    @mcp.tool()
Behavior4/5

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

The description implies a read-only listing operation with no side effects, which is adequate for a simple listing tool. However, it could more explicitly state it's non-destructive, but given no annotations, the clarity is sufficient.

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?

Two sentences, no wasted words, purpose first then usage context. Extremely concise and well-structured.

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

Completeness5/5

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

Given the tool has no parameters and an output schema exists, the description provides complete context: what it does and when to use it. The sibling list provides additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters, so schema coverage is 100%. The description adds no parameter details, which is fine as none are needed. Baseline of 4 is appropriate.

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 it lists every PPM action/wizard tool with a one-line description, distinguishing it from individual action sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides guidance on when to use the tool: when deciding between calling a custom tool or falling back to generic Odoo MCP tools like update_record/search_records, with specific alternative names.

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