Skip to main content
Glama
Odoo Connect MCP

Odoo Connect MCP

by Tristan439

Getting started

getting_started
Read-onlyIdempotent

Explains what you can ask about an Odoo instance based on granted access and provides example questions to clarify available read-only capabilities.

Instructions

Explains what you can ask about this Odoo given the access the user granted, with example questions. Use when the user asks what you can do.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context: the answer is conditioned on the access the user granted, so results are permission-scoped rather than universal. It also tells the agent the response contains worked example questions, which shapes how to relay it.

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?

Two short sentences, no filler, with the capability statement front-loaded and the trigger condition second. Every clause carries information an agent needs.

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-parameter, read-only discovery tool with no output schema and full annotation coverage, this says enough to select and call it correctly. A brief note on what the output looks like structurally (e.g., a list of apps/models plus sample prompts) would close the remaining gap.

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 nothing for the description to explain beyond what the empty schema already shows. Baseline applies with no gaps to compensate for.

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 and resource: explains what can be asked of this Odoo instance, scoped to the user's granted access, and includes example questions. This is distinguishable from siblings like list_models or describe_model, which enumerate schema rather than usage. It stops short of a 5 only because it doesn't explicitly name how it differs from those introspection tools.

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

Usage Guidelines4/5

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

Gives an explicit trigger condition: 'Use when the user asks what you can do.' That is a clear when-to-use signal an agent can act on. No exclusions or named alternatives are provided, so a 4 rather than a 5.

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