Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

merge_customers

Destructive

Merge a duplicate customer into the one to keep by moving licenses, marketplace and Discord accounts, filling empty fields, and deleting the duplicate. This cannot be undone; confirm first.

Instructions

Merge a duplicate customer into another: its licenses, marketplace and Discord accounts move over, empty fields are filled in, and the duplicate is deleted. Can't be undone. Confirm with the user first.

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": {
      "into": "<into>",
      "from": "<from>"
    },
    "name": "merge_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesthe duplicate (id or email): its licenses and accounts move to 'into', then it is deleted
intoYesthe customer to keep (id or email)

Output Schema

NameRequiredDescriptionDefault
mergedYesthe customer that was kept
deletedYesthe duplicate's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotency, but the description earns its keep by disclosing exactly what data migrates, that empty fields on the target get populated, and that the source record is destroyed and irrecoverable. Those migration details are not encoded anywhere in the structured fields.

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: what it does, what happens to the data, the danger, and the confirmation requirement. Front-loaded with the action and free of padding.

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

Completeness4/5

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

For a two-parameter destructive mutation with full annotation coverage and an output schema, the description supplies the essential behavior and the safety warning. It could note what happens on conflicting non-empty fields or whether the merge is transactional, but nothing critical to correct invocation is missing.

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 coverage is 100% and both parameter descriptions already explain directionality ('from' is the duplicate that moves and is deleted, 'into' is the keeper). The description's list of migrated assets gives useful context but does not add syntax or constraints beyond what the schema states.

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 ("Merge a duplicate customer into another") and immediately enumerates the semantics of the merge: licenses, marketplace and Discord accounts transfer, empty fields are filled, duplicate is deleted. This is clearly distinguishable from siblings like delete_customer or list_customers because the merge behavior is spelled out.

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?

Usage context is clear: this is the tool for consolidating a duplicate customer, and a procedural prerequisite ("Confirm with the user first") is given. It stops short of naming an alternative such as delete_customer for the case where a duplicate should simply be removed rather than merged.

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