Skip to main content
Glama
Odoo MCP Server

Odoo MCP Server

by rizkyagung18

get_sales_orders

Read-only

Retrieve sales orders and quotations, newest first, including customer, total and invoice status. Filter by state to view draft quotations, sent quotes, confirmed orders or cancellations.

Instructions

List sales orders and quotations, newest first, with customer, total and invoice status.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to return (1-50).
stateNodraft = quotation, sent = quotation sent to customer, sale = confirmed sales order, cancel = cancelled. Omit for all.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds that results are newest-first and that quotations are mixed in with confirmed orders, but says nothing about pagination behavior, total result counts, or any scope/permission constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. The trailing 'with customer, total and invoice status' overlaps with the existing output schema, so it is slightly redundant but not wasteful.

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?

With an output schema present, the description need not explain return values, and both optional parameters are fully documented in the schema. The only real gap is routing guidance relative to sibling tools like get_unpaid_invoices.

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 description coverage is 100%, including the state enum mapping (draft/sent/sale/cancel), so the schema carries the parameter burden. The description adds only the 'newest first' ordering hint and does not supplement or reinterpret either parameter.

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 and resource ('List sales orders and quotations') plus ordering ('newest first') and returned fields, so an agent knows exactly what it retrieves. It does not explicitly distinguish itself from overlapping siblings such as get_unpaid_invoices, which keeps it out of 5 territory.

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 by the purpose: an agent can infer this lists orders/quotations, but the description never states when to prefer it over get_unpaid_invoices or when not to use it. No prerequisites, scoping, or exclusions are given.

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