Skip to main content
Glama

Create Customer Tool

create-customer
Idempotent

Creates one customer directly in the selected FieldRobin business when the connection has customer-write permission. Search first to avoid creating a duplicate; reuse the idempotency key only when retrying the same request. Use to create customer in the connected business. Returns capability, status, approval_required, persisted, agent_run_id, scope, customer, result, idempotent_replay, message.

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": {
      "name": "<name>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create-customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCustomer full name.
emailNoCustomer email address, if known.
notesNoInternal customer notes.
phoneNoCustomer phone number, if known.
addressNoCustomer address, if known.
trade_typeNoCustomer trade or service type.
location_idNoBusiness location for the customer.
business_nameNoCustomer business name, if known.
lifecycle_tagNoLifecycle tag.
idempotency_keyYesOpaque retry key. Reuse it only for the same request to receive the verified result without creating a duplicate.
acquisition_sourceNoHow the customer was acquired.

Output Schema

NameRequiredDescriptionDefault
scopeYesBusiness boundary used to authorize this result.
resultYesVerified domain result and tenant-scoping evidence.
statusYesAuthoritative mutation outcome.
messageYesHuman-readable completion message.
customerYesSafe projection of the created record.
persistedYesWhether the record was persisted.
capabilityYesExecuted domain capability name.
agent_run_idYesAuditable agent run identifier.
approval_requiredYesWhether additional approval is required.
idempotent_replayYesTrue when this repeats an already verified request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "agent_run_id": {
      +      "description": "Auditable agent run identifier.",
      +      "type": "integer"
      +    },
      +    "approval_required": {
      +      "description": "Whether additional approval is required.",
      +      "type": "boolean"
      +    },
      +    "capability": {
      +      "description": "Executed domain capability name.",
      +      "type": "string"
      +    },
      +    "customer": {
      +      "description": "Safe projection of the created record.",
      +      "type": "object"
      +    },
      +    "idempotent_replay": {
      +      "description": "True when this repeats an already verified request.",
      +      "type": "boolean"
      +    },
      +    "message": {
      +      "description": "Human-readable completion message.",
      +      "type": "string"
      +    },
      +    "persisted": {
      +      "description": "Whether the record was persisted.",
      +      "type": "boolean"
      +    },
      +    "result": {
      +      "description": "Verified domain result and tenant-scoping evidence.",
      +      "type": "object"
      +    },
      +    "scope": {
      +      "description": "Business boundary used to authorize this result.",
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "Authoritative mutation outcome.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "capability",
      +    "status",
      +    "approval_required",
      +    "persisted",
      +    "agent_run_id",
      +    "scope",
      +    "customer",
      +    "result",
      +    "idempotent_replay",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (which already declare idempotentHint=true and destructiveHint=false), the description discloses the customer-write permission prerequisite and the idempotency-key retry contract. The return-field list also hints at an approval_required/persisted workflow, which is useful context the annotations do not convey, though it never explains what happens when a duplicate or approval block occurs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The useful content (permission gate, dedupe, retry key) is front-loaded, but the third sentence duplicates the first and the trailing enumeration of return fields is redundant given an output schema exists. Two of five sentences do not earn their place.

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?

With an output schema present, the description needn't explain return values, and it covers the key behavioral facts an agent needs: permission requirement, dedupe-first policy, and idempotent retry. It is only slightly incomplete in not stating how duplicate or approval-required outcomes surface to the caller.

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 description coverage is 100%, so every one of the 11 parameters is already documented, including the idempotency_key retry semantics. The description's idempotency note largely restates the schema text and adds no format or constraint detail beyond it, so the baseline of 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?

The opening sentence gives a specific verb and resource ("Creates one customer") plus scope ("directly in the selected FieldRobin business"), which is enough to distinguish it from read-side siblings like get-customer or customer-service-requests. It stops short of naming an alternative tool, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives real pre-call guidance: search first to avoid duplicates, and reuse the idempotency key only when retrying the same request. It does not name which search tool to use or state when not to call this at all, and the closing "Use to create customer in the connected business" adds nothing beyond the first sentence.

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