Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

delete_customer

Destructive

Moves a customer to Trash and stops their licenses from working at once; restore within 30 days. Confirm with the user first.

Instructions

Move a customer to the Trash with their licenses: those stop working at once. They can be restored for 30 days with restore_from_trash. To combine duplicates use merge_customers instead. 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": {
      "customer": "<customer>"
    },
    "name": "delete_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerYesthe customer's id or email

Output Schema

NameRequiredDescriptionDefault
noteYes
trashedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds what annotations cannot: licenses stop working immediately, the trash is recoverable for exactly 30 days, and restoration is done via a named sibling. That is substantive consequence disclosure for a destructive mutation.

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 ordered by importance: what happens, how to undo, what to use instead, then the safety gate. No filler, and the destructive consequence is front-loaded.

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?

For a one-parameter destructive mutation with an output schema available, the description covers side effects, reversibility window, alternative tool, and confirmation requirement. Nothing an agent needs to call it safely 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 the single parameter already documents "the customer's id or email," so the description adds no identifier format or resolution detail. Baseline 3 applies since the schema carries the parameter semantics fully.

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 ("Move a customer to the Trash with their licenses") and immediately scopes the blast radius. It explicitly separates this tool from merge_customers and points at restore_from_trash, so an agent can distinguish it from siblings without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit routing: use merge_customers for duplicates, restore_from_trash to undo, plus a procedural prerequisite ("Confirm with the user first"). Both the when and the when-not are named.

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