MCP Advbox Server

advbox_create_customer

Create a customer record in Advbox by providing user ID, origin ID, and name, with optional contact and address details.

Instructions

Create a new customer in Advbox. Requires user ID, origin ID, and customer name.

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": {
      "users_id": "<users_id>",
      "customers_origins_id": "<customers_origins_id>",
      "name": "<name>"
    },
    "name": "advbox_create_customer"
  }
}

Input Schema

Name	Required	Description
`city`	No	City
`name`	Yes	Customer name
`email`	No	Customer email address
`notes`	No	Additional notes
`phone`	No	Phone number (99999999999 or (99) 99999-9999)
`state`	No	State (e.g., SP, RJ)
`document`	No	Customer document number
`users_id`	Yes	ID of the user creating the customer
`birthdate`	No	Birthdate (YYYY-MM-DD)
`cellphone`	No	Cellphone number
`occupation`	No	Occupation/profession
`postalcode`	No	Postal code (99999-999)
`identification`	No	Customer CPF/CNPJ (e.g., 123.456.789-01)
`customers_origins_id`	Yes	ID of the customer origin

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.4/5.0

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 of behavioral disclosure. It only states the creation action without mentioning permissions, side effects, return values, or reversibility. For a mutating operation, this is insufficient.

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 concise sentence that clearly states the action and required inputs. It is front-loaded with the primary purpose and contains no superfluous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 14 parameters, no output schema, and no annotations, this description is too minimal. It lacks usage context, behavioral details, and return format. Although the schema covers parameter descriptions, the overall description does not provide sufficient context for an agent to fully understand when and how to use the tool.

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%, so all 14 parameters have descriptions. The description repeats the required parameters (users_id, customers_origins_id, name) but adds no extra meaning beyond what the schema already provides. Baseline 3 applies because the schema handles parameter semantics.

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 uses a specific verb and resource: 'Create a new customer in Advbox.' It clearly identifies the action and the target entity, and the required fields add specificity. This distinguishes it from sibling tools like advbox_create_movement or advbox_create_task by naming the customer resource.

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 states prerequisites ('Requires user ID, origin ID, and customer name') but does not explicitly provide when-to-use guidance or mention alternatives. Usage is implied by the action, but no exclusions or alternative tool references are given.

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

Deploy Server