Odoo MCP Server

search_holidays

Read-onlyIdempotent

Search holidays within a specified date range, optionally filtering by employee ID to retrieve leave records from Odoo for planning and reporting.

Instructions

Search for holidays within a date range

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "search_holidays"
  }
}

Input Schema

Name	Required	Description
`end_date`	Yes	End date in YYYY-MM-DD format.
`instance`	No	Optional configured Odoo instance name; uses the default if omitted.
`start_date`	Yes	Start date in YYYY-MM-DD format.
`employee_id`	No	Optional employee ID used to filter holidays.

Output Schema

Name	Required	Description
`error`	No	Error message, if any
`result`	No	List of holidays found
`success`	Yes	Indicates if the search was successful

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.2.1Jul 15, 2026
- addedInput schema / properties / employee_id / description
```
Added value: +"Optional employee ID used to filter holidays."
```
- addedInput schema / properties / end_date / description
```
Added value: +"End date in YYYY-MM-DD format."
```
- addedInput schema / properties / instance / description
```
Added value: +"Optional configured Odoo instance name; uses the default if omitted."
```
- addedInput schema / properties / start_date / description
```
Added value: +"Start date in YYYY-MM-DD format."
```

Changed1 schema field changedv1.0.0Jun 12, 2026

addedInput schema / properties / instance

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Instance"
+}

First observedv0.2.0Apr 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description does not add any behavioral context beyond what annotations provide, such as pagination or filtering behavior.

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 a single short sentence that is front-loaded with the key action and resource, containing no unnecessary words.

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?

Given the tool's simplicity, presence of an output schema, and comprehensive annotations, the description is sufficient for understanding the tool's purpose. It could mention that it returns a list of holidays, but the output schema likely covers that.

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 description coverage is 100% with each parameter adequately described. The tool description adds no additional parameter meaning 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 clearly states the tool searches for holidays within a date range. The verb 'Search' and resource 'holidays' are specific, and it distinguishes from sibling search tools like search_records or search_employee.

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 usage for date-range holiday searches but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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