Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

delete_license

Destructive

Moves a license to the Trash so it stops validating immediately, while staying restorable for 30 days. Use it to deactivate a key quietly, then confirm with the user first.

Instructions

Move a license to the Trash: it stops working at once (validation answers as for an unknown key) and can be restored for 30 days with restore_from_trash. Unlike revoke_license, nothing is announced and it can come back. 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": {
      "license": "<license>"
    },
    "name": "delete_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
licenseYesthe license id, key, the start of its key, or the customer's email

Output Schema

NameRequiredDescriptionDefault
noteYes
trashedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the immediate-effect semantics (validation behaves as for an unknown key), the 30-day restore window with the exact restoring sibling named, and the fact that unlike revoke nothing is announced to the customer. The annotations already cover destructiveness, so this added operational context is the value here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core effect front-loaded, followed by the disambiguation and the confirmation requirement. No filler, though the parenthetical about validation answers is slightly dense.

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?

An output schema exists so return values need no explanation, and the description still covers effect timing, reversibility window, restore path, customer-visible impact, and the confirmation step. Nothing an agent needs before invoking this destructive tool 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 license parameter already documents that an id, key, key prefix, or customer email is accepted. The description adds no further parameter meaning, so the baseline 3 applies.

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 license to the Trash") and immediately scopes what that means. It distinguishes itself from revoke_license by name, so an agent can pick between the two without opening either schema.

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?

Explicitly contrasts with revoke_license (silent vs announced, reversible vs not) and gives a concrete procedural instruction: confirm with the user first. Both the when-to-use condition and the safety precondition are stated.

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