Skip to main content
Glama
odoo-mcp

odoo-mcp

by affifariza04

sales_report

Read-only

Generates confirmed sales reports between two ISO dates, grouped by month, customer, or product for revenue analysis.

Instructions

Confirmed sales between two ISO dates (inclusive), grouped by month, customer or product.

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": {
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "sales_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toYes
group_byNomonth
date_fromYes

Output Schema

NameRequiredDescriptionDefault
rowsYes
date_toYes
group_byYes
date_fromYes
total_revenueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: the range is inclusive on both ISO-format boundaries, and results only cover confirmed sales, which is a real filtering semantic an agent would otherwise miss. It does not mention pagination or the shape of grouped output, but an output schema exists.

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 front-loaded sentence: resource, filter, and grouping in the order an agent needs them. No filler, no restatement of the tool name.

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 3-parameter read-only aggregation tool with annotations and an output schema, the description covers scope, date semantics, and grouping options. Minor gaps remain: it does not clarify what 'confirmed' excludes (e.g., drafts vs cancelled) or what happens when the range yields nothing.

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?

Schema description coverage is 0%, so the description must carry the load, and it does: it pins date_from/date_to to ISO format and declares the range inclusive, and it names the three grouping dimensions for group_by. It does not specify parameter interaction (e.g., date ordering) or timezone handling, keeping it just short of a 5.

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+resource pair ('Confirmed sales') plus scope qualifiers: an ISO date range and the grouping dimension. The word 'Confirmed' narrows the record type, so an agent can tell it apart from a generic search/listing tool; however, no sibling tool is named or excluded, so the differentiation is implicit rather than explicit.

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?

Usage is only implied: 'Confirmed sales' signals that unconfirmed/draft transactions are out of scope, and the group_by enum indicates aggregatable dimensions. There is no explicit when-to-use/when-not-to-use statement and no named alternative among check_stock, overdue_invoices, or search_records.

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