Skip to main content
Glama
Odoo MCP Server

Odoo MCP Server

by rizkyagung18

search_partners

Read-only

Find Odoo customers and contacts by name, email, or phone to locate partner records. Search companies or individuals before creating or updating records.

Instructions

Find customers and contacts (Odoo partners) by name, email or phone.

Partners are companies or individual people; individuals may belong to a company.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_partners"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to return (1-50).
queryYesText to look for in the name, email or phone.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 safety is covered. The description adds genuine domain structure — that a partner may be a company or an individual, and that individuals can belong to a company — which affects how results should be interpreted. It does not, however, disclose matching semantics (partial vs. exact, case sensitivity), ranking, or what happens with zero results.

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?

Two short sentences, front-loaded with the action and resource. The second sentence is a domain gloss that earns most of its place by clarifying company/individual relationships, though the stray line break adds no structure.

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, return values need not be explained, and both parameters are fully documented. What remains thin is matching behavior — whether the query does substring or exact matching and how name/email/phone are combined — which matters for a search tool but is a modest gap.

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%: 'query' is already documented as text to look for in name, email or phone, and 'limit' with default 10, range 1-50. The description restates the same field list without adding syntax, format, or matching-behavior detail, so the baseline 3 applies.

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?

Names a specific verb and resource: "Find customers and contacts (Odoo partners)" by "name, email or phone". The parenthetical maps the domain term 'partner' to customers/contacts, so an agent knows exactly what entity set is queried. It doesn't explicitly distinguish itself from siblings like list_leads or get_sales_orders, but the resource is concrete enough to be separable.

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?

Usage is only implied: 'find ... by name, email or phone' suggests lookup-style retrieval, but there is no statement of when to prefer this over list_leads or other sibling tools, nor any precondition such as needing an identifier first. An agent must infer the search context.

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