Skip to main content
Glama

create_contact

Add new contacts to Odoo CRM with details like name, email, phone, address, and company relationships to manage customer and supplier records.

Instructions

    Create a new contact.

    Args:
        name: Contact name
        email: Email address (optional)
        phone: Phone number (optional)
        is_company: True if it's a company, False for individual
        customer: Mark as customer (default: True)
        supplier: Mark as supplier (default: False)
        street: Address (optional)
        city: City (optional)
        zip_code: Zip code (optional)
        parent_id: Parent company ID for contacts (optional)

    Returns:
        Confirmation with created contact ID
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
emailNo
phoneNo
is_companyNo
customerNo
supplierNo
streetNo
cityNo
zip_codeNo
parent_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden. While it states the tool creates a contact and returns a confirmation with ID, it lacks critical behavioral details: whether this requires specific permissions, if it's idempotent, what happens on duplicate contacts, error conditions, or rate limits. The description covers basic functionality but misses important operational context.

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?

The description is well-structured with clear sections for Args and Returns, making it easy to parse. It's appropriately sized for a tool with many parameters, though the introductory sentence is minimal. Every sentence adds value, with no redundant information.

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 the tool's complexity (10 parameters, 1 required) and the presence of an output schema (implied by 'Returns'), the description is reasonably complete. It documents all parameters thoroughly and states the return value. However, without annotations, it could better address behavioral aspects like error handling or side effects.

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

Parameters5/5

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

The description adds substantial value beyond the input schema, which has 0% description coverage. It provides clear semantics for all 10 parameters, explaining what each represents (e.g., 'Contact name', 'True if it's a company'), noting optionality, and specifying defaults (e.g., 'default: True' for customer). This fully compensates for the schema's lack of descriptions.

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 clearly states the tool's purpose: 'Create a new contact.' It uses a specific verb ('create') and identifies the resource ('contact'), making the action unambiguous. However, it doesn't differentiate from sibling tools like 'get_contact' or 'list_contacts' beyond the obvious create vs. read distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), when not to use it, or how it relates to sibling tools like 'get_contact' or 'list_contacts' for contact management workflows.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/industream/mcp-odoo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server