Skip to main content
Glama
odoo-mcp

odoo-mcp

by affifariza04

create_quotation

Create a draft sales quotation from a customer and product lines, then show a summary for human confirmation before anything is confirmed or sent.

Instructions

Create a DRAFT sales quotation. The human sees a summary and must confirm; nothing is confirmed or sent.

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": {
      "customer_id": "<customer_id>",
      "lines": "<lines>"
    },
    "name": "create_quotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYes
customer_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only say it is a non-read-only, non-destructive, non-idempotent, closed-world write; the description adds genuinely new behavior: the output is a draft, a human reviews a summary, and nothing is confirmed or sent. It does not address the non-idempotent hint (whether repeated calls create duplicate drafts) or permission requirements, which keeps it from a 5.

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?

Two short sentences with no filler, and the important state (DRAFT) plus the confirmation gate are front-loaded. Nothing could be removed without losing meaning.

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?

An output schema exists, so return values need no explanation, and the two-parameter shape is simple. However, the completely undocumented parameter semantics (lines structure, positive quantity) and the unaddressed repeat-call behavior leave gaps for a write tool that constructs a multi-line document.

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 description coverage is 0% and the description says nothing about customer_id or the lines array, whose nested QuoteLine requires product_id and a positive quantity. With two required parameters and an unlabeled nested item schema, the description should have explained what a line is and what constraints apply, and it does not.

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?

The description states a specific verb and resource ('Create a ... sales quotation') and pins down the resulting state as a DRAFT, which is a real distinguishing detail. It does not explicitly contrast with any sibling, but the sibling list (stock, customers, invoices, reports, records) has no overlapping create-quotation tool, so ambiguity is low.

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?

It conveys that the operation is a pre-confirmation draft step, implying when in a workflow to call it, but gives no explicit when-to-use, when-not-to-use, or alternative tool routing. An agent must infer that a different (unlisted) path confirms or sends a quotation.

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