Skip to main content
Glama

create_customer

Add a new customer to the CRM with deduping. Supports confirm and idempotency validation.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe full name of the customer
tagsNoOptional search tags
emailNoOptional email (checked for deduping)
notesNoOptional customer notes (max 2000 characters)
phoneNoOptional phone number (checked for deduping)
farmIdYesThe unique farm ID
addressNoOptional street address
confirmNoSet to true to commit, false for dry-run preview
birthdayNoOptional customer birthday (YYYY-MM-DD format)
idempotencyKeyNoUnique request idempotency key
marketingOptInNoMarketing and Plunk opt-in (defaults to false)
shippingAddressNoOptional structured shipping address object

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / birthday
      Added value: +{
      +  "description": "Optional customer birthday (YYYY-MM-DD format)",
      +  "type": "string"
      +}
    • addedInput schema / properties / notes
      Added value: +{
      +  "description": "Optional customer notes (max 2000 characters)",
      +  "type": "string"
      +}
    • addedInput schema / properties / shippingAddress
      Added value: +{
      +  "description": "Optional structured shipping address object",
      +  "properties": {
      +    "city": {
      +      "type": "string"
      +    },
      +    "country": {
      +      "type": "string"
      +    },
      +    "state": {
      +      "type": "string"
      +    },
      +    "street1": {
      +      "type": "string"
      +    },
      +    "zip": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The description adds real behavior beyond the annotations: dedupe matching and a confirm/idempotency pathway that annotations do not express. However, it never says what happens when a duplicate is found (error, merge, or return existing), nor what the default is if confirm is omitted — the single most consequential behavior for a create tool. Note the mild tension: idempotentHint=false while the description advertises 'idempotency validation' via an explicit key.

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?

Two short sentences, front-loaded with the action and resource; nothing is padded. 'Supports confirm and idempotency validation' is slightly vague phrasing ('validation' of what?) but costs little space.

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?

For a 12-parameter mutation with a nested object and no output schema, the description covers the two things an agent most needs to know exist (dedupe, dry-run) but omits duplicate-handling outcome, whether confirm defaults to no-op or commit, and any permission or farmId scoping context.

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 the schema already documents all 12 parameters including the nested shippingAddress, confirm dry-run, and idempotencyKey. The description only adds the general note that deduping applies (the schema already flags email and phone as 'checked for deduping'), so baseline 3 applies.

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?

States a specific verb and resource: 'Add a new customer to the CRM', plus a differentiating trait ('with deduping'). It doesn't name the sibling it is not (update_customer, get_customer_details), so an agent must infer create-vs-update from the verb alone.

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 explicit when-to-use, when-not-to-use, or alternative routing is given, even though update_customer and get_customer_details sit right next to it in the sibling list. 'Supports confirm and idempotency validation' hints at a preview flow but never says when an agent should reach for it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources