Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar

createCustomer

createCustomer

Creates a new customer record in the billing system, supporting address, tax identifiers, contact details, and custom data fields.

Instructions

Creates a new customer in the system with various attributes including address, tax info, and contact details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
external_idNoExternal customer ID (optional).
customer_nameYesCustomer name (required).
emailNoCustomer primary email address (optional).
phone_numberNoCustomer phone number (optional).
address_line1NoAddress line 1 (optional).
address_line2NoAddress line 2 (optional).
address_line3NoAddress line 3 (optional).
address_cityNoAddress city (optional).
address_stateNoAddress state (optional).
address_zipCodeNoAddress zip code (optional).
address_countryNoAddress country (optional).
address_country_codeNoAddress country code (optional).
ship_to_line1NoShipping address line 1 (optional).
ship_to_line2NoShipping address line 2 (optional).
ship_to_line3NoShipping address line 3 (optional).
ship_to_cityNoShipping address city (optional).
ship_to_stateNoShipping address state (optional).
ship_to_zipCodeNoShipping address zip code (optional).
ship_to_countryNoShipping address country (optional).
ship_to_country_codeNoShipping address country code (optional).
communications_enabledNoEnable/disable communications (defaults to true).
auto_charge_enabledNoEnable/disable auto-charge (defaults to true).
business_entity_idNoBusiness entity ID (UUID format, optional).
custom_dataNoCustom key-value pairs for additional customer info (e.g., {"industry": "saas", "account_tier": "enterprise", "sales_rep": "jane"}). Optional.
tax_infoNoList of tax identifiers. Each item: {country_code, tax_code, tax_id}. country_code uses mixed ISO formats (e.g. 'USA', 'IND', 'AUS', 'EU', 'GB'/'UK', 'SG', 'JP', 'BR', 'CA', and 2-letter codes for EU members like 'DE', 'FR', 'IT'). tax_code varies by country — common pairings: VAT (most of EU + UK + CH + most of MENA + IL/PH/ZA/EG/JO etc.), GST (India, Australia, Singapore), GST/HST (Canada), GST/IRD (NZ), TIN (USA, Qatar, Kuwait, Iraq, Libya), JCT (Japan), CNPJ (Brazil), SST (Malaysia), NPWP (Indonesia), MVA (Norway). Pair country_code + tax_code correctly. Optional.
__userContextNoInternal user context for multi-tenant authentication and approval workflow
Behavior2/5

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

No annotations provided; description only says 'Creates' without disclosing side effects, permissions, idempotency, rate limits, or error conditions. The internal __userContext parameter is not mentioned in the description.

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?

Single sentence of 14 words, front-loaded with the action. Efficient but could be slightly expanded for clarity without losing conciseness.

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

Completeness1/5

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

Desperately incomplete for 26 parameters and no output schema. Missing return value info, error handling, authentication context, and behavioral details. The description adds almost no value beyond the schema.

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 baseline is 3. Description adds no additional meaning beyond summarizing parameter categories; it does not compensate with extra context.

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?

Description clearly states 'Creates a new customer' with a brief mention of attributes. It distinguishes from 'updateCustomer' but not from 'createCustomerAddress', which also deals with addresses.

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?

No guidance on when to use this tool vs alternatives, no prerequisites mentioned, and no when-not-to-use advice. Given 30+ sibling tools, this is a significant gap.

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/zenskar/mcp-zenskar'

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