Skip to main content
Glama

Odoo

by io.github.pipeworx-io

Odoo List Crm Leads

odoo_list_crm_leads
Read-onlyIdempotent

List Odoo CRM leads & opportunities (crm.lead). Returns name, contact, email_from, expected_revenue, probability, stage_id, and type (lead/opportunity). Use for "open opportunities" or "sales pipeline".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dbYesOdoo database name.
urlYesOdoo instance base URL, e.g. https://mycompany.odoo.com (trailing slash optional). Works for Odoo Online and self-hosted.
typeNoFilter by record type: "lead" or "opportunity". Omit for both.
limitNoMax records (default 20).
_apiKeyYesOdoo API key (Settings → Account Security → API Keys) or account password.
usernameYesOdoo login email.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds value by specifying returned fields (name, contact, email_from, etc.) and the filter option by type, without contradicting annotations.

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?

The description is composed of two concise sentences: the first describes purpose and returns, the second gives a usage hint. No extraneous information, effectively front-loaded.

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?

The description includes the model name, return fields, and usage context, compensating for the lack of output schema. However, it does not mention pagination or sorting behavior, though the limit parameter in schema covers basic pagination.

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% with descriptions for all 6 parameters. The tool description does not add additional input parameter details beyond what the schema provides; it focuses on return values. Baseline 3 applies.

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 'List Odoo CRM leads & opportunities', specifying the verb 'List' and resource 'CRM leads & opportunities', and mentions the model crm.lead. It also lists returned fields, distinguishing it from siblings like odoo_list_invoices or odoo_list_sale_orders.

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?

The description provides a usage hint ('Use for "open opportunities" or "sales pipeline"'), giving clear context. However, it does not explicitly state when not to use the tool or name alternative tools, which would warrant a 5.

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

All Odoo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

Some tools have overlapping purposes (e.g., ask_pipeworx and ask_pipeworx_grounded; multiple Polymarket analysis tools) but descriptions help differentiate. Odoo-specific tools are distinct among themselves but muddled with many general-purpose tools.

Naming Consistency2/5

Naming is heavily inconsistent: Odoo tools follow 'odoo_list_*' pattern while others use varied structures like verb-first (forget, remember) or noun-first (entity_profile, recent_alerts). No unified verb_noun pattern across the set.

Tool Count3/5

At 32 tools, the server exceeds the typical well-scoped range (3–15) but is not excessively large. Many tools are generic and could be trimmed, making the set feel heavier than necessary.

Completeness2/5

Despite many tools, the server lacks essential CRUD operations for Odoo (e.g., create/update/delete leads) and the 'Odoo' name misrepresents the actual focus. Gaps in Odoo functionality and mixed domains create a sense of incompleteness.

Resources