Skip to main content
Glama
Odoo MCP Server

Odoo MCP Server

by rizkyagung18

list_leads

Read-only

Retrieve CRM leads and opportunities sorted by highest expected revenue. Filter by stage to answer pipeline questions and identify your biggest prospects.

Instructions

List CRM leads and opportunities, highest expected revenue first.

Use for questions like "what's in the pipeline?", "show deals in Proposition"
or "who are our biggest prospects?". Each record has type "lead" (not yet
qualified) or "opportunity" (in the sales pipeline). `total` is the number of
matching records; `leads` holds at most `limit` of them.

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": "list_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to return (1-50).
stageNoFilter by stage name, case-insensitive partial match (e.g. 'New', 'Qualified', 'Proposition', 'Won'). Omit for all stages.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 useful behavioral detail — revenue ordering and the lead-vs-opportunity record distinction — but says nothing about pagination, truncation behavior, or whether `total` reflects filters, leaving the transparency burden partly unmet.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and ordering, followed by usage examples, then output semantics. It is efficient overall, though the final sentence on `total` and `leads` partially restates what the output schema already covers.

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?

With an output schema present and rich annotations, the description covers the essentials: what is listed, the ordering, and the two record types. The main omission is any note on truncation or how `total` interacts with `limit` filtering.

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?

Schema coverage is 100%, so both `limit` and `stage` are already documented with defaults and ranges in the schema. The description only alludes to `limit` via 'leads holds at most limit' and adds nothing about stage filtering or case-insensitive matching beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List CRM leads and opportunities') plus a defined ordering ('highest expected revenue first'). It does not explicitly differentiate itself from the nearby sibling pipeline_summary, so it stops short of a 5.

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?

Concrete example questions ('what's in the pipeline?', 'show deals in Proposition') give an agent clear context for when this tool fits. It offers no exclusions or named alternatives, so it stays at 4 rather than 5.

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