retailcrm-mcp

create_customer

Create a new customer record with name, contact details, and address. Returns success status and customer ID.

Instructions

Create a customer with name, contacts, address, optional externalId. Returns {success, id}.

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": {
      "first_name": "<first_name>"
    },
    "name": "create_customer"
  }
}

Input Schema

Name	Required	Description
`site`	No	Site (store) symbolic code. Required on create/edit when the API key is scoped to multiple sites (see list_sites).
`email`	No	Customer email
`phones`	No	Array of phone numbers
`last_name`	No	Customer last name
`first_name`	Yes	Customer first name
`patronymic`	No	Customer patronymic (middle name)
`external_id`	No	External system ID for linking
`address_city`	No	City
`address_text`	No	Full address as free text
`address_region`	No	Region/state

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Jul 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description does not need to cover safety. It adds the return value ({success, id}) and highlights 'optional externalId', which provides some behavioral context beyond annotations. However, it does not discuss permissions, idempotency, or other operational nuances.

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 a single, front-loaded sentence that clearly states the action and resource, lists major inputs, and includes the return value. Every word earns its place; there is no redundancy or fluff.

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 10 parameters and no output schema, the description provides a solid high-level overview and the return shape. It does not repeat schema details, which is fine. However, it doesn't mention edge cases like the conditional requirement for 'site' when the API key is scoped to multiple stores, but that is covered in the schema. Overall, sufficient for the tool's complexity.

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 coverage is 100% with detailed descriptions for all 10 parameters. The tool description summarizes them as 'name, contacts, address, optional externalId' but does not add new semantic meaning beyond what the schema already provides. Baseline 3 is appropriate when the schema fully documents parameters.

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 states the action ('Create') and the resource ('a customer'), and lists key fields ('name, contacts, address, optional externalId') which distinguishes it from sibling tools like update_customer or list_customers. It also includes the return format ({success, id}), making the purpose unambiguous.

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?

The description implies usage for creating a new customer but does not explicitly state when to use this tool versus alternatives like update_customer or merge_customers. There is no mention of exclusions or prerequisites, so guidance is only implicit from the verb 'Create'.

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