SalesHookAI

Update customer

updateCustomer

Idempotent

Updates an existing customer: address, phone, e-mail, name, company, notes, status, customer type or custom fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "updateCustomer"
  }
}

Input Schema

Name	Required	Description
`name`	No	New name
`email`	No	New email
`notes`	No	New notes
`phone`	No	New phone number
`status`	No	New status (active, inactive)
`address`	No	New address
`company`	No	New company name
`customerId`	No	ID of the customer to update
`customValues`	No	Custom field values to set, e.g. [{fieldId, value}]
`customerName`	No	Name search to find the customer
`customerType`	No	New customer lifecycle type (lead, prospect, new_customer, regular_customer, inactive)
`customerSince`	No	Date the customer became a customer (YYYY-MM-DD)
`lastContactAt`	No	Last contact date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already declare readOnly=false, destructive=false, and idempotent=true, so the safety profile is covered. The description adds the scope of updatable fields, but it does not disclose whether this is a partial update, what happens to unspecified fields, or what occurs if the customer cannot be found.

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 definition is a single front-loaded sentence with no filler. It states the action, target, and field scope efficiently.

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?

With 13 optional parameters, no output schema, and a mutation operation, the description is only minimally complete. The schema and annotations carry much of the burden, but the description does not explain customer identification or partial-update behavior, which are important for correct invocation.

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%, establishing a baseline of 3. The description enumerates several update fields but does not add format, syntax, or identification semantics beyond the schema, and it omits several parameters such as customerId, customerName, customerSince, and lastContactAt.

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 description uses a specific verb and resource: 'Updates an existing customer,' and enumerates many mutable fields. This clearly distinguishes an update from a create, but it does not explicitly distinguish it from the sibling saveCustomer.

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

Usage Guidelines3/5

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

'Existing customer' implies this is for modifying an already-known customer rather than creating one. However, the description gives no explicit when-to-use guidance, no exclusions, and no mention of how to identify the customer via customerId or customerName.

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

All SalesHookAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?