Skip to main content
Glama

ppm_status_report_print_url

Retrieve the URL to view a status report as a PDF in Odoo. Provide a report ID to get the direct download link.

Instructions

Return the Odoo URL for the PDF render of a status report.

Odoo returns a report action; the caller fetches the PDF via that URL using the same credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
report_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the ppm_status_report_print_url MCP tool. Calls Odoo's action_print_report on ppm.status.report and returns the action (URL) along with the report_id.
    @mcp.tool()
    def ppm_status_report_print_url(report_id: int) -> dict[str, Any]:
        """Return the Odoo URL for the PDF render of a status report.
    
        Odoo returns a report action; the caller fetches the PDF via that URL
        using the same credentials.
        """
        action = client().call_action("ppm.status.report", "action_print_report", [report_id])
        return {"report_id": report_id, "action": action}
  • Registration via the @mcp.tool() decorator, which registers the function as an MCP tool named 'ppm_status_report_print_url'.
    @mcp.tool()
  • Helper method on OdooClient that invokes the action method via execute_kw. Called by the handler to trigger action_print_report.
    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])
Behavior3/5

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

With no annotations, the description must disclose behavior. It states the return is a URL and how to use it, but does not mention potential errors (e.g., invalid report_id) or side effects. Adequate but minimal.

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 covering all necessary information without redundancy. Every word contributes to understanding the tool's purpose and usage.

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

Completeness4/5

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

Given a single parameter and an output schema (present but not shown), the description covers the core functionality. Some might want error handling details, but for a straightforward URL retrieval, this is sufficient.

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

Parameters3/5

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

Only one required parameter (report_id) with 0% schema coverage. The description does not elaborate on report_id beyond implicit context. Adds no new meaning compared to the schema, but the simple integer type needs little explanation.

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 tool returns the Odoo URL for a PDF render of a status report, with a specific verb and resource. It distinguishes itself from sibling tools like ppm_status_report_generate or ppm_status_report_publish by focusing on URL retrieval.

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

Usage Guidelines4/5

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

Provides a brief usage hint: 'the caller fetches the PDF via that URL using the same credentials.' While it doesn't explicitly compare with alternatives, it gives practical context for invoking the tool correctly.

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