Skip to main content
Glama
Sign In
Odoo Claude MCP

Odoo Claude MCP

by rosenvladimirov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

user_connection_activate

Activate a personal connection by alias to set it as the working connection for Odoo interactions.

Instructions

Activate one of your personal connections as the working connection.

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": {
      "alias": "<alias>"
    },
    "name": "user_connection_activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasYesConnection name to activate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided. The description does not disclose effects of activation (e.g., deactivates previous connection, whether it's idempotent, or any side effects). For a tool with no annotations, more transparency is needed.

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?

Single, front-loaded sentence with no wasted words. The key action and object are immediately clear.

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?

For a simple activation tool with one parameter and no output schema, the description is minimally adequate but lacks mention of what happens on success or failure, or the return value.

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 coverage is 100% with a single parameter. The description adds no extra meaning beyond the schema's 'Connection name to activate'. Baseline score 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 clearly states the tool activates a personal connection as the working connection, which is a specific verb-resource pair. It distinguishes from sibling tools like user_connection_add, user_connection_delete, and user_connection_list.

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?

No explicit guidance on when to use this tool versus alternatives. The context implies it's for switching connections, but no when-not-to-use or mentions of other tools for managing connections.

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

Deploy Server

Other Tools