Skip to main content
Glama
Odoo Connect MCP

Odoo Connect MCP

by Tristan439

List apps

list_apps
Read-onlyIdempotent

Retrieve Odoo apps with installation status and the user's granted access level (none/read) to see which data an AI assistant can query.

Instructions

Lists the Odoo apps, whether they are installed, and the access level the user granted for each (none/read).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is covered. The description adds genuine value by disclosing the payload shape — installed vs. not, and per-app access level with the enum values '(none/read)' — which is the main behavioral unknown for a discovery tool.

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 with no filler, and the resource plus the returned attributes are front-loaded. Every clause earns its place by adding either scope or payload 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 zero-argument read tool backed by four annotations, the definition covers what the agent most needs: what is listed and what each entry conveys. Minor gaps remain — ordering, pagination or result-size expectations, and whether uninstalled apps are included by default — but these are small for this complexity level.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain; baseline for an empty schema is 4. The description correctly implies that no filtering arguments exist, so nothing is silently omitted.

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 ('Lists the Odoo apps') and goes further by stating the attributes returned: install status and the user's access level per app. It does not explicitly distinguish itself from siblings like list_models, but the resource is concrete enough that an agent can tell it apart.

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: an agent infers this is the tool to call when it needs to discover which apps exist and what the user can touch. There is no explicit when-to-use statement, no exclusion of alternatives (e.g., list_models), and no prerequisite such as needing a connection first.

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