Skip to main content
Glama
Sign In
odoo-mcp-server

odoo-mcp-server

by Calderkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List available models

odoo_list_models
Read-onlyIdempotent

Discover Odoo models you can query, including technical name, label, admin hint, and write permissions. Filter by keyword to find the right model before describing fields or searching records.

Instructions

List the Odoo models (tables) you may query, all in one response: technical name, label, the administrator's hint about what each one holds, and can_write (whether changes are allowed on it). Only models enabled by the administrator that you can read are included. Use it to find a model name you do not know yet; use odoo_describe_model for a model's fields and odoo_search for its records.

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

Input Schema

NameRequiredDescriptionDefault
searchNoCase-insensitive text matched against the technical name, label and hint, e.g. 'invoice'. Omit to list every model.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • changedInput schema / properties / search / description
      Previous value: -"Optional text to filter models."New value: +"Case-insensitive text matched against the technical name, label and hint, e.g. 'invoice'. Omit to list every model."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real scope information beyond them — that only administrator-enabled, readable models appear, and that can_write signals whether mutation is permitted on a given model. What it omits is scale behavior, e.g. roughly how many models come back or whether there is any cap, but 'all in one response' implies no pagination.

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 what is returned and how it differs from neighbors, in two tight sentences with no filler. Slightly dense in the first sentence's parenthetical enumeration, but nothing is wasted.

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?

A single optional parameter, no output schema, and the description already enumerates the return fields plus the inclusion rule, which is enough to call it correctly. Minor omission is any sense of result volume for a no-filter call.

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%, so the single 'search' parameter is already fully documented (case-insensitive match against name, label, hint; omit to list all). The description adds no parameter-level meaning beyond that, so the 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?

A specific verb and resource ('List the Odoo models (tables) you may query') plus an explicit enumeration of the returned fields (technical name, label, hint, can_write). It also names the sibling tools it is not, so an agent can separate it from odoo_describe_model and odoo_search without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the selecting condition directly: 'Use it to find a model name you do not know yet,' and routes the alternatives to odoo_describe_model for fields and odoo_search for records. Both when-to-use and when-to-use-something-else are covered.

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

Deploy Server

Other Tools