Skip to main content
Glama
Sign In
odoo-mcp-server

odoo-mcp-server

by Calderkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Current user and date

odoo_context
Read-onlyIdempotent

Returns the Odoo session context: current user, company, currency, time zone, today's date and UTC time. Use it to resolve relative dates like 'last quarter' or the current user and company.

Instructions

Return the session context: who you are connected as (user id, name, login), the current company and its currency, the companies you can access, language, time zone, today's date in that time zone ('YYYY-MM-DD'), the current UTC date and time ('YYYY-MM-DD HH:MM:SS') and the Odoo version. Use it to resolve relative dates such as 'last quarter', the current user or company, or the current company's currency. It reads no business records. No arguments.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/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 still adds real value by stating it reads no business records, takes no arguments, and, importantly, enumerating the returned fields in the absence of an output schema.

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?

It is front-loaded with the core purpose, followed by a usage sentence and two short constraints. The field enumeration is long but earns its place because no output schema exists to document the return values elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 context tool with no output schema, the description covers purpose, return contents, date formats, and usage guidance. Nothing an agent needs in order 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.

Parameters4/5

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

There are zero parameters, so the baseline is 4. The description reinforces this explicitly with 'No arguments', leaving no ambiguity about how to invoke it.

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 opens with a specific verb and resource ('Return the session context') and enumerates exactly what is inside it: user id/name/login, company, currency, accessible companies, language, time zone, both date formats, and Odoo version. This makes it unmistakable against the data-oriented siblings like odoo_read or odoo_search.

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?

It gives explicit positive guidance ('Use it to resolve relative dates such as last quarter, the current user or company, or the current company's currency') and adds a clarifying exclusion ('It reads no business records'), which steers an agent away from using it as a record-fetch tool. It does not name a specific sibling alternative, so it falls just short of the top tier.

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