Skip to main content
Glama
Sign In
Odoo Claude MCP

Odoo Claude MCP

by rosenvladimirov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ai_usage_log_stats

Get billing ledger KPIs including totals, per-model breakdown, 30-day trends, and error analysis for AI usage logs.

Instructions

Dashboard KPIs for the billing ledger: totals, per-model breakdown, 30-day timeseries, recent errors, derived metrics (cache hit rate, avg cost per billed doc, monthly €).

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

Input Schema

NameRequiredDescriptionDefault
periodNomonth
connectionNodefault
tenant_codeNoTenant slug. Derived from connection if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Without annotations, the description carries full burden. It correctly indicates a read-only operation (stats), but doesn't disclose potential behaviors like required permissions, rate limits, or data refresh semantics. The derived metrics detail adds some transparency, but safety aspects are missing.

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?

A single, well-structured sentence that front-loads the key value ('Dashboard KPIs') and lists specific outputs. Every word earns its place—no fluff, high information density.

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?

Given no output schema, the description adequately covers return values by listing metric categories. However, it could specify the time window for '30-day timeseries' more precisely and mention if totals are aggregated across all time. Still, it's largely complete for its purpose.

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

Parameters2/5

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

Schema coverage is only 33% (period has description). The description does not add meaning to 'connection' or 'tenant_code' parameters. The overall tool description helps but doesn't compensate for the low per-parameter documentation.

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 provides 'Dashboard KPIs for the billing ledger' and enumerates specific metrics (totals, per-model breakdown, timeseries, errors, derived metrics), making the purpose explicit and distinguishing it from sibling tools like ai_usage_log_query.

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?

The description implies usage for aggregate stats, but lacks explicit guidance on when to use versus alternatives like ai_usage_budget_status or ai_usage_log_query. However, the mention of 'Dashboard KPIs' provides clear context for data exploration.

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