odoo-mcp

Overview Schema Source Related Servers Discussions Admin

odoo_demo_questionnaire

Qualify prospects before building a demo by presenting a structured questionnaire. It records missing answers as hypotheses, then drafts a demo plan for validation before any writing.

Instructions

Questionnaire de qualification, avant de batir une demo prospect.

Presente-le tel quel, preambule compris. N'invente pas les reponses manquantes : signale tes hypotheses. Puis compose le plan et fais-le valider AVANT d'ecrire.

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_demo_questionnaire"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.9.0Aug 11, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It discloses critical behavioral traits: the questionnaire must be presented verbatim including the preamble, missing answers must not be invented but signaled as hypotheses, and a plan must be validated before any writing. This is rich, specific guidance that goes far beyond a generic tool description.

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?

Three short sentences, purpose first, each sentence carries a distinct operational directive. There is no filler or redundancy; the description is economical and front-loaded.

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?

The description provides a complete mini-workflow for the agent: present questionnaire, annotate assumptions, compose plan, validate before writing. Since an output schema exists, return values need not be described. For a zero-parameter tool, this is fully sufficient for correct usage.

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?

The tool has zero parameters, so the input schema is trivially complete. The description does not need to explain parameters, and the baseline for 0 parameters is 4. No parameter-related information is missing.

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 identifies the tool as a qualification questionnaire for prospect demos, using a specific noun phrase and explicit instructions to present it as-is. This distinguishes it from sibling tools like odoo_demo_mode or odoo_presentation_guide, which serve different demo-related purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use this tool ('avant de batir une demo prospect') and provides a step-by-step workflow: present the questionnaire verbatim, flag missing answers as hypotheses, compose a plan, and get validation before writing. This is explicit and actionable, leaving no ambiguity about usage.

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