Skip to main content
Glama
Odoo MCP Server

Odoo MCP Server

by rizkyagung18

pipeline_summary

Read-only

Summarizes active sales opportunities by stage, showing counts, expected revenue, and win-probability-weighted revenue.

Instructions

Summarize the sales pipeline: number of opportunities and expected revenue per stage.

weighted_revenue = expected revenue x win probability. Covers active
opportunities only (not unqualified leads, not lost/archived deals).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pipeline_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the useful scope constraint and the weighted_revenue formula. It does not state the time window covered or whether results are cached/precomputed, which an agent would need to interpret the numbers.

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 tight sentences with the core output description front-loaded, then a formula definition and scope limits. Every sentence earns its place and nothing is redundant.

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?

An output schema exists, so return values need not be spelled out, yet the description still defines the weighted_revenue metric, which helps interpretation. The one omission is the time period the summary covers, a notable gap given there are no filter parameters to constrain it.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to compensate for. The schema is an empty object and the description correctly does not invent parameter explanations.

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?

States a specific verb ('Summarize') and resource ('the sales pipeline') plus the exact output shape: opportunity count and expected revenue per stage. None of the siblings (create_lead, list_leads, get_sales_orders, get_unpaid_invoices, search_partners) performs an aggregation, so no sibling disambiguation is required.

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?

Scope is explicitly bounded: active opportunities only, excluding unqualified leads and lost/archived deals, which tells the agent when this tool's output is and is not authoritative. It does not name an alternative tool for lead-level or deal-level detail, but the exclusions cover the main misuse risk.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.