Skip to main content
Glama
optimize-overseas

LACRM MCP Server

Create Contact

create_contact

Add a new person or company to Less Annoying CRM by providing name, assigned user, and record type. Optionally include contact details, addresses, and custom fields.

Instructions

Create a new contact or company in Less Annoying CRM.

PREREQUISITES (call these first):

  1. get_contact_schema (or get_company_schema for companies) → see ALL fields (required and optional), their types, and formats

  2. get_users → get valid user IDs for the required assigned_to field

Use this tool when you need to add a new person or company to the CRM. Set is_company to true to create a company record instead of a person.

Supports flat-string shortcuts: use email_address, phone_number, or website_url for single values instead of the array format. Supports custom_field_names for name-based custom field resolution.

Returns the new ContactId on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull name of the contact or company name
emailNoEmail addresses array
phoneNoPhone numbers array
addressNoPhysical addresses
websiteNoWebsite URLs
birthdayNoBirthday in yyyy-mm-dd format. Use 0000-mm-dd for annual dates.
addressesNoAlias for "address" (accepted for compatibility).
job_titleNoJob title/position
is_companyYesSet true to create a company, false for a person
assigned_toYesUser ID to assign the contact to. Use get_users to find valid IDs.
website_urlNoSingle website URL. For multiple websites, use website array instead.
company_nameNoCompany name (for contacts). Creates company if not exists.
phone_numberNoSingle phone number (auto-converts to Work type). For multiple phones, use phone array instead.
custom_fieldsNoCustom field values keyed by field NAME, written verbatim with no dropdown validation (LACRM v2 ignores ID-keyed custom-field writes). Prefer custom_field_names for validated writes. Mutually exclusive with custom_field_names.
email_addressNoSingle email address (auto-converts to Work type). For multiple emails, use email array instead.
background_infoNoAdditional notes/background
custom_field_namesNoCustom field values keyed by field name (case-insensitive; validated against the account fields + dropdown options, then written by name). Mutually exclusive with custom_fields.
Behavior4/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 of behavioral disclosure. It discloses the return value (ContactId), explains flat-string shortcuts for single values, and mentions custom_field_names for name-based resolution. It also tells the agent to call schema/users first. However, it does not explicitly mention side effects like auto-creating a company via company_name, which is left to the schema 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?

The description is concise and well-structured: a clear purpose line, followed by prerequisites in a block, then usage guidance, and then key behavioral notes. Every sentence adds value, with no redundancy. The line breaks improve readability.

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?

Given the tool's complexity (17 parameters, nested objects, no output schema), the description covers prerequisites, usage, return value, and special input modes. Combined with the fully described schema, this gives the agent all necessary information to invoke the tool correctly. There is no major gap.

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 coverage is 100%, so the baseline is 3. The description adds meaning beyond individual schema descriptions by grouping email_address/phone_number/website_url as 'flat-string shortcuts' and explaining the advantage of custom_field_names over custom_fields. This helps the agent understand input patterns not evident from the schema alone.

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 opens with 'Create a new contact or company in Less Annoying CRM' — a specific verb+resource+system statement. It clearly distinguishes this tool from siblings like edit_contact, delete_contact, and get_contact by focusing solely on creation, and explicitly mentions the is_company flag to create company records.

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?

The description explicitly states when to use this tool: 'Use this tool when you need to add a new person or company to the CRM.' It also provides required prerequisites (get_contact_schema/get_company_schema, get_users) and explains how to switch between person and company creation via is_company. This is strong when-to-use guidance.

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/optimize-overseas/lacrm-mcp'

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