Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

update_customer

Change a customer's email, name, notes, or Discord link; omitted fields stay unchanged and empty strings clear them.

Instructions

Change a customer's email, name, notes or Discord link. Fields left out stay as they are; an empty string clears one. When the new email belongs to another customer, merge the two with merge_customers instead.

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

Input Schema

NameRequiredDescriptionDefault
nameNoa new name; empty string clears it
emailNoa new email; empty string clears it
notesNonew notes; empty string clears them
customerYesthe customer's id or email
discordUserIdNothe customer's Discord user id; empty string unlinks it

Output Schema

NameRequiredDescriptionDefault
customerYesthe customer after the change

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is partly covered; the description adds genuinely new behavior: partial-update semantics and the fact that an empty string actively clears a field. That clearing behavior is a form of data removal the annotations do not surface, and the description deserves credit for it, though it does not mention reversibility or required permissions.

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?

Three short sentences, front-loaded with what changes and followed by the patch contract and the routing exception. Every clause carries information; nothing is redundant with the title or the schema.

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?

With an output schema present and annotations covering safety, the description only needs to cover mutation semantics and disambiguation, and it does both: partial update, empty-string clearing, and the merge escape hatch. Nothing an agent needs to call this 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%, so the baseline is 3, but the description adds meaning the schema does not: it frames all optional fields as an all-or-nothing patch ("Fields left out stay as they are") and defines the empty-string sentinel for clearing. It also adds a cross-parameter rule for email collisions that no single schema field captures.

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 opening sentence gives a specific verb ("Change") plus the exact resource fields it touches (email, name, notes, Discord link), and the final sentence explicitly names merge_customers as a different tool for a different case. An agent can tell this apart from delete_customer or merge_customers without opening the schema.

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 provides a clear conditional rule for when NOT to use this tool: if the new email belongs to another customer, use merge_customers instead. It also states the patch contract (omitted fields unchanged, empty string clears), so usage is well bounded, though it says nothing about when to prefer a full create/delete flow or any permission prerequisites.

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