Shopmonkey MCP Server

update_customer

Keep customer records accurate by updating their address, city, state, ZIP, or name using the customer ID. Modify existing customer information in Shopmonkey.

Instructions

Update an existing customer's information.

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": {
      "id": "<id>"
    },
    "name": "update_customer"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The customer ID to update
`zip`	No	ZIP code
`city`	No	City
`state`	No	State
`address`	No	Street address
`lastName`	No	Customer last name
`firstName`	No	Customer first name

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.1Sep 8, 2026

removedInput schema / properties / email

Removed value: -{
-  "description": "Customer email address",
-  "type": "string"
-}

removedInput schema / properties / phone

Removed value: -{
-  "description": "Customer phone number",
-  "type": "string"
-}

First observedv1.0.0Mar 26, 2026

TDQS

C2.8/5.0

Behavior1/5

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

No annotations are provided, and the description does not disclose any side effects, permissions, or consequences of the update operation. The term 'update' implies modification, but the description does not explicitly state the impact or any associated risks.

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 a single, concise sentence with no extraneous words or redundant information. It is well-structured and directly conveys the tool's function.

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

Completeness2/5

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

Given the simplicity of the operation, the description is minimal but lacks any context about when to use it, how it relates to other customer tools, or any behavioral details. Without annotations, the description alone is insufficient for a user to fully understand the tool's role.

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?

The schema provides descriptions for all 7 parameters (100% coverage), so the baseline is 3. The tool description itself adds no additional semantic meaning beyond the field descriptions already present.

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 explicitly states the action (update) and the resource (customer), clearly distinguishing it from create_customer and get_customer. It is unambiguous and concise.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives like create_customer or search_customers. There is no mention of prerequisites, typical scenarios, or conditions for selection.

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

Deploy Server