Skip to main content
Glama

mcp

by com.crisphive

updateCustomer

Idempotent

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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoThe response payload. Omitted on error unless the error carries structured data.
errorsNoField-level validation details; present only for VALIDATION_ERROR responses.
messageNoHuman-readable message ("Success" or an error description), localized via the X-Locale header.
error_codeNo0 on success; a stable string error code on failure (e.g. CUSTOMER_NOT_FOUND).

TDQS

A4.6/5.0
Behavior5/5

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

Goes far beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true) by disclosing the full edge-case behavior: empty-string clearing per field, enum empty values ignored, full_name immutability-at-empty, the address object's all-or-nothing replacement with geocoding of missing coordinates, and the PHONE_OR_EMAIL_REQUIRED refusal. The partial-update semantics are consistent with idempotentHint=true; no contradiction.

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?

The description is long but every sentence carries a distinct behavioral rule, and the front-loaded 'PARTIAL update' framing plus the enumerated clearable-field list makes it scannable. Minor redundancy with per-field schema descriptions ('Omit to leave unchanged...' appears in both) slightly inflates length, but the density is warranted for a 12-parameter update tool.

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?

Complete for the most error-prone update tool in the family: 12 parameters, a nested address block, enum quirks, and a cross-field invariant are all covered, and the output schema exists so return values need no explanation. Nothing an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and each parameter description already documents omit-vs-clear behavior, so the baseline is 3. The description adds the cross-parameter synthesis that per-field schema text cannot: which fields accept empty-string clearing, the enum/full_name exceptions, the address geocoding rule, and the contact-channel invariant tying phone and email together. This is genuine added meaning, though it partly restates what the schema already says.

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?

States a specific verb and resource ('Update a customer') and immediately shores up scope with 'PARTIAL update — send only the fields you are changing', which distinguishes it from createCustomer and deleteCustomer. The verb-resource pairing plus the partial-update framing makes tool selection unambiguous.

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?

Provides clear context on when to use it — the 'two-way CRM sync friendly: push one field from your system of record without re-sending the record' framing explains the exact workflow this tool is designed for. It does not explicitly name alternatives or exclusions (e.g., 'use createCustomer for new records'), leaving sibling routing to the agent.

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

All mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools target a distinct resource and action, and the heavy use of noun-qualified names (listJobRequestBookingWindows vs listMatchingSlots vs listNearbyTechnicians) keeps close concepts separable. A few availability/skill-listing endpoints could be misselected on first pass, but their descriptions are specific enough to recover.

Naming Consistency4/5

The dominant pattern is clear camelCase verb_noun: createCustomer, getTechnician, listSkills, replaceTechnicianBuddies, previewJobRequestMove. Slight irregularities exist (quoteJobRequest and confirmJobRequest are action-style rather than resource-CRUD, and listJobRequestChanges vs listJobRequests mixes singular/plural), but the overall convention is predictable.

Tool Count2/5

43 tools is well above the 25+ threshold for 'too many', even for a broad field-service domain. The emergency flow alone has three dedicated endpoints and the many replaceTechnician* tools could plausibly be consolidated without hurting clarity.

Completeness2/5

Customer, technician, and job-request reading/creation are well covered, plus a rich scheduling/move/emergency surface. However, the job lifecycle is incomplete: there is no update, cancel, delete, assign, or complete endpoint, and reference entities like vehicles, job types, service areas, and skills lack write operations.

Resources