Skip to main content
Glama
Odoo Connect MCP

Odoo Connect MCP

by Tristan439

List models of an app

list_models
Read-onlyIdempotent

Lists the technical models available for read access within a specified Odoo app, helping you identify tables such as sale.order for sales.

Instructions

Lists the technical models (tables) you may read in an app, e.g. app="sales" → sale.order, sale.order.line.

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": {
      "app": "<app>"
    },
    "name": "list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesApp key from list_apps, e.g. "crm", "sales", "inventory"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered structurally. The description's one added behavioral detail is that results are permission-scoped ('models you may read'), which is real value, but it says nothing about ordering, completeness, or pagination of the returned list.

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?

One sentence that front-loads the verb and resource and ends with a compact illustrative example. No filler, no restatement of the title, nothing that could be cut without losing information.

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?

For a single-parameter, read-only listing tool with full annotation coverage and no output schema, the description does the essential job: it says what comes back (technical model names) and in what scope (readable ones). A note on ordering or whether access-denied models are omitted would make it airtight, but nothing needed to call it correctly is missing.

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% and the single app parameter is documented in the schema with its own examples ('crm', 'sales', 'inventory'). The description's example clarifies what that key produces rather than adding syntax or format constraints beyond the schema, 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?

"Lists the technical models (tables) you may read in an app" states a specific verb and resource, and the concrete mapping example (app="sales" → sale.order, sale.order.line) makes the output tangible. It does not explicitly distinguish itself from sibling describe_model, but the verb 'lists' versus 'describes' plus the access-scoping phrase is enough for an agent to separate them.

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: the schema note 'App key from list_apps' establishes the chaining order, which is genuinely useful guidance. There is no explicit statement of when to prefer this over describe_model or list_apps, and no exclusions, so it lands at minimum-viable rather than strong.

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