Skip to main content
Glama

ppm_status_report_publish

Publish a draft status report by providing its report ID.

Instructions

Publish a draft status report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
report_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'ppm_status_report_publish' tool. It calls the Odoo action 'action_publish' on model 'ppm.status.report' with the given report_id, then reads back and returns the report's name, state, and project_id.
    @mcp.tool()
    def ppm_status_report_publish(report_id: int) -> dict[str, Any]:
        """Publish a draft status report."""
        client().call_action("ppm.status.report", "action_publish", [report_id])
        return _read_state("ppm.status.report", report_id, ["name", "state", "project_id"])
  • The tool is registered via the @mcp.tool() decorator on line 130, which registers it with the FastMCP server instance 'mcp'.
    @mcp.tool()
    def ppm_status_report_publish(report_id: int) -> dict[str, Any]:
        """Publish a draft status report."""
        client().call_action("ppm.status.report", "action_publish", [report_id])
        return _read_state("ppm.status.report", report_id, ["name", "state", "project_id"])
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It merely states 'Publish', which suggests finalizing a report, but does not disclose side effects, state changes, permissions required, or what happens to the draft after publishing.

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 extremely concise at 5 words, but this brevity comes at the cost of missing critical information. It is front-loaded but incomplete.

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?

The tool has an output schema (not shown), yet the description does not explain what 'publish' entails in terms of state changes, prerequisites, or consequences. The agent lacks context to safely invoke this tool.

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?

Schema description coverage is 0%, but the description does not explain the meaning or format of the report_id parameter. The agent must infer from the name alone, failing to add value beyond the schema.

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 'Publish a draft status report' clearly states the verb (publish) and resource (draft status report), effectively distinguishing it from sibling tools like ppm_status_report_generate, ppm_status_report_print_url, and ppm_status_report_reset_draft.

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 when to use (when a draft report is ready to publish), but provides no explicit guidance on prerequisites, when not to use, or alternatives. Sibling tools are available but no differentiation is given.

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