Skip to main content
Glama

ppm_export_budget

Export budget lines to an XLSX file with optional filters by project, portfolio, date, category, or include closed items. Returns a direct download URL.

Instructions

Export budget lines to XLSX. Returns the download URL action.

At least one of project_id or portfolio_id is typically set; omit both to export everything visible to the service user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNo
portfolio_idNo
date_fromNo
date_toNo
category_idNo
include_closedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for ppm_export_budget tool. It collects optional parameters (project_id, portfolio_id, date_from, date_to, category_id, include_closed) into a dictionary and delegates to _run_export_wizard('ppm.budget.export.wizard', vals).
    @mcp.tool()
    def ppm_export_budget(
        project_id: int | None = None,
        portfolio_id: int | None = None,
        date_from: str | None = None,
        date_to: str | None = None,
        category_id: int | None = None,
        include_closed: bool = False,
    ) -> dict[str, Any]:
        """Export budget lines to XLSX. Returns the download URL action.
    
        At least one of `project_id` or `portfolio_id` is typically set; omit both
        to export everything visible to the service user.
        """
        vals: dict[str, Any] = {"include_closed": include_closed}
        if project_id is not None:
            vals["project_id"] = project_id
        if portfolio_id is not None:
            vals["portfolio_id"] = portfolio_id
        if date_from:
            vals["date_from"] = date_from
        if date_to:
            vals["date_to"] = date_to
        if category_id is not None:
            vals["category_id"] = category_id
        return _run_export_wizard("ppm.budget.export.wizard", vals)
  • The shared helper _run_export_wizard creates a wizard record via execute_kw, calls the action_export method, and returns the resulting download URL action.
    def _run_export_wizard(
        model: str,
        values: dict[str, Any],
    ) -> dict[str, Any]:
        wizard_id = client().execute_kw(model, "create", [values])
        action = client().call_action(model, "action_export", [wizard_id])
        # action is `ir.actions.act_url` with /web/content/{attachment_id}?download=true
        return {"wizard": model, "action": action}
  • The tool is registered via the @mcp.tool() decorator on line 372, which binds it into the FastMCP server as the 'ppm_export_budget' tool.
    @mcp.tool()
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It correctly indicates a read-only export and the output as a download URL, but lacks details on authentication, rate limits, or whether the operation is synchronous.

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 concise sentences with no wasted words. The purpose is front-loaded and the usage tip follows efficiently.

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 having an output schema, the description omits crucial details for a 6-parameter tool: no explanation of date formats, category usage, or include_closed semantics. The behavioral note on scope is helpful but insufficient.

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?

Schema description coverage is 0%, yet the description only adds meaning for project_id and portfolio_id. The other four parameters (date_from, date_to, category_id, include_closed) are not explained at all.

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?

Clearly states the action (export) and resource (budget lines to XLSX). It also mentions the return value (download URL). This distinguishes it from sibling export tools like ppm_export_resources and ppm_export_risks.

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 explicit guidance on when to set project_id/portfolio_id and the effect of omitting both. However, it does not compare itself to sibling tools or state when not to use this tool.

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