Skip to main content
Glama
crisphive

Crisphive

Official
by crisphive
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Update a customer

updateCustomer
Idempotent

Partially update a customer record: send only the fields you are changing, leave omitted values untouched, clear fields with empty strings, and replace the address block with geocoding when provided.

Instructions

Update a customer

PARTIAL update — send only the fields you are changing; anything you OMIT is left exactly as stored (two-way CRM sync friendly: push one field from your system of record without re-sending the record). To CLEAR a field, send it as an empty string: uid, phone, email, notes, preferred_technician_id, service_area_id. tier and status are enums with no empty member, so an empty value there is ignored rather than stored. full_name cannot be set to empty. The nested address object is all-or-nothing: omit it to leave the stored address (and its coordinates) untouched; when present it REPLACES the whole block, and missing latitude/longitude are geocoded from the address. A customer must keep at least one contact channel — an update that would clear both phone and email is refused with PHONE_OR_EMAIL_REQUIRED.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCustomer ID (UUID)
uidNoYour external reference for this customer. Omit to leave unchanged, "" to clear. Max 32 chars.
tierNoLoyalty tier. Omit to leave unchanged; "" is ignored (an enum has no empty member).
emailNoEmail address. Omit to leave unchanged, "" to clear.
notesNoFree-form internal notes about the customer. Omit to leave unchanged, "" to clear; max 4000 chars.
phoneNoPhone number in E.164 international format (`+16135550188`); a bare national number is rejected with PHONE_INVALID — see createCustomerReq.Phone. Omit to leave unchanged, "" to clear. 10–20 chars.
statusNoLifecycle status. Omit to leave unchanged; "" is ignored.
addressNoPostal address and coordinates. Omit the whole object to leave the stored address untouched; when present it REPLACES the address block.
full_nameNoCustomer's full name. Omit to leave unchanged; an empty or blank value is ignored (a customer cannot be left nameless). Max 255 chars.
sms_opt_inNoSMS consent, tri-state: omit/null = leave unchanged; true = grant (only when the customer explicitly consented — the original consent timestamp is preserved); false = revoke (opt-out, stops SMS immediately).
service_area_idNoUUID of the service area for this customer. Omit to leave unchanged, "" to clear. Must belong to this business.
preferred_technician_idNoUUID of the technician this customer prefers. Omit to leave unchanged, "" to clear. Must belong to this business.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv0.1.1
    • changedInput schema / properties / address / description
      Previous value: -"Postal address and coordinates."New value: +"Postal address and coordinates. Omit the whole object to leave the stored address untouched; when present it REPLACES the address block."
    • changedInput schema / properties / email / description
      Previous value: -"Email address."New value: +"Email address. Omit to leave unchanged, \"\" to clear."
    • changedInput schema / properties / full_name / description
      Previous value: -"Customer's full name. Required; max 255 chars."New value: +"Customer's full name. Omit to leave unchanged; an empty or blank value is ignored (a customer cannot be left nameless). Max 255 chars."
    • changedInput schema / properties / notes / description
      Previous value: -"Free-form internal notes about the customer; max 4000 chars."New value: +"Free-form internal notes about the customer. Omit to leave unchanged, \"\" to clear; max 4000 chars."
    • changedInput schema / properties / phone / description
      Previous value: -"Phone number. 10–20 chars."New value: +"Phone number in E.164 international format (`+16135550188`); a bare\nnational number is rejected with PHONE_INVALID — see createCustomerReq.Phone.\nOmit to leave unchanged, \"\" to clear. 10–20 chars."
    • changedInput schema / properties / preferred_technician_id / description
      Previous value: -"UUID of the technician this customer prefers. Must belong to this business."New value: +"UUID of the technician this customer prefers. Omit to leave unchanged, \"\" to clear. Must belong to this business."
    • changedInput schema / properties / service_area_id / description
      Previous value: -"UUID of the service area for this customer. Must belong to this business."New value: +"UUID of the service area for this customer. Omit to leave unchanged, \"\" to clear. Must belong to this business."
    • changedInput schema / properties / status / description
      Previous value: -"Lifecycle status."New value: +"Lifecycle status. Omit to leave unchanged; \"\" is ignored."
    • changedInput schema / properties / tier / description
      Previous value: -"Loyalty tier."New value: +"Loyalty tier. Omit to leave unchanged; \"\" is ignored (an enum has no empty member)."
    • changedInput schema / properties / uid / description
      Previous value: -"Your external reference for this customer. Optional; max 32 chars."New value: +"Your external reference for this customer. Omit to leave unchanged, \"\" to clear. Max 32 chars."
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "full_name"
-]New value: +[
+  "id"
+]
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly=false, idempotent=true, destructive=false. The description adds substantial behavioral detail: omitted fields are left unchanged, empty strings clear fields, enum empty values are ignored, full_name cannot be emptied, address replacement is all-or-nothing with geocoding, and clearing both contact channels is refused. This is rich, non-obvious behavior that the annotations alone cannot convey.

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 dense but every clause earns its place. The most important caveat — partial update semantics — is front-loaded, and the subsequent rules cover clearing, enums, address replacement, and validation without repetition or filler.

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

Completeness5/5

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

For a complex 12-parameter mutation with many edge cases, the description covers all critical update behaviors, including an explicit error condition. No output schema exists, so the absence of return-value documentation is not a significant gap given how thoroughly the operation's semantics are specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds cross-cutting parameter semantics that tie the schema together: which fields accept empty-string clearing, how enum empty values are handled, the tri-state nature of sms_opt_in, and the all-or-nothing address object. This materially improves an agent's ability to construct correct update payloads.

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 states a clear verb and resource: update an existing customer. It goes further by immediately characterizing the operation as a PARTIAL update, which distinguishes it from create/delete/get siblings even without naming them.

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?

The title and lead sentence establish clear context for modifying an existing customer, and the partial-update semantics make the intended use unambiguous. However, it does not explicitly contrast with createCustomer, getCustomer, or deleteCustomer, so it lacks an explicit when-not-to-use statement.

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

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