odoo-safe-mcp

odoo_list_models

Read-onlyIdempotent

List installed business models with technical names and labels, optionally filtering by search text for read-only discovery.

Instructions

List installed business models (technical name and label), optionally filtered by text. Read-only.

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

Name	Required	Description	Default
`limit`	No
`search`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.0Oct 22, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the trailing 'Read-only.' is redundant. The one genuine addition is 'installed' — the scope excludes uninstalled/custom models — but nothing is said about pagination or the default 50-item cap.

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?

A single front-loaded sentence with no wasted words. The appended 'Read-only.' is the only dead weight, since it just repeats the annotation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema and annotations cover return shape and safety, so no gap there. The definition is still incomplete on the limit parameter and result-set bounding, which an agent needs before calling on a large Odoo instance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry both parameters. It only addresses 'search' obliquely ('filtered by text') and never mentions 'limit' or its default of 50, leaving half the parameter surface undocumented.

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+resource ('List installed business models') and names the returned fields (technical name and label), which distinguishes it from odoo_describe_model and the data-query siblings. No explicit sibling callout, so not 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 Guidelines3/5

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

'Optionally filtered by text' implies when to pass search, but there is no guidance on when to pick this over odoo_search or odoo_describe_model (e.g. discovery vs introspection). Usage is only inferable.

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

Deploy Server