Skip to main content
Glama
Odoo Connect MCP

Odoo Connect MCP

by Tristan439

Check Odoo connection

check_connection
Read-onlyIdempotent

Tests the connection to Odoo and explains any problem in plain words, helping you diagnose access or configuration issues before running queries.

Instructions

Tests the connection to Odoo and explains any problem in plain words. Use it first when something fails.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 openWorldHint=false, so the safety profile is fully covered by structured data. The description adds value beyond that by disclosing the return behavior: it explains problems 'in plain words', which tells the agent to expect human-readable diagnostics rather than a raw error object. It does not mention latency or what a healthy response looks like, keeping it just under a 5.

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, zero filler, with the purpose stated before the usage cue. Nothing could be removed 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 simple zero-parameter diagnostic with no output schema, the description supplies both what it does and when to reach for it, plus a hint that failures are reported in plain language. Only a note on what a successful result contains is missing, which is minor 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 schema semantics to add meaning to. The baseline for a parameterless tool 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?

The description states a specific verb and resource ('Tests the connection to Odoo'), which is inherently distinct from the data-oriented siblings like read_records and search_records. An agent can identify this as the diagnostic/preflight tool without opening any schema.

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?

'Use it first when something fails' gives clear, actionable timing for invoking the tool. It stops short of explicit when-not conditions or naming alternatives, but for a zero-parameter connectivity check the guidance covers the realistic decision point.

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