Skip to main content
Glama

create_customer

Add a new customer to the system using first name, last name, and email. Optionally include business name, locale, phone, currency, and tax exemption.

Instructions

Create a new customer. POST /customers. Required: firstName, lastName, email. Optional: businessName, locale, phoneNum, phoneExt, preferredCurrency, taxExempt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firstNameYesCustomer first name (required)
lastNameYesCustomer last name (required)
emailYesCustomer email (required)
businessNameNoBusiness name
localeNoLocale code
phoneNumNoPhone number
phoneExtNoPhone extension
preferredCurrencyNoPreferred currency code
taxExemptNoWhether customer is tax exempt
Behavior2/5

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

With no annotations present, the description must disclose behavioral traits. It reveals the HTTP method and field requirements but omits side effects (e.g., duplicate email handling), idempotency, authorization needs, or error behavior.

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 two concise sentences, front-loaded with the core purpose, and contains no extraneous information.

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

Completeness3/5

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

While the description covers input parameters, it lacks information about the output (e.g., returns created customer ID) and does not address potential conflicts or limitations, leaving gaps despite the tool's simplicity.

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 descriptive parameter descriptions. The description restates required/optional fields, adding minimal value beyond the schema.

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 a new customer'), includes the HTTP method and endpoint, and lists required and optional fields. This distinguishes it from siblings like create_currency or create_invoice, which serve different entities.

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 the tool is for creating customers but does not specify when to use it versus alternatives like update_customer, nor does it provide exclusions or context-dependent 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/rhinosaas/rebillia-mcp-server'

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