Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

rotate_license_key

Destructive

Replaces a leaked or shared license key with a new one for the same license and machines, invalidates the old key, and emails the customer; confirm before running.

Instructions

Give a license a new key: the same license and machines, the old key refused from now on, and the customer emailed the new one. For a key that leaked or was shared. The answer has the new key masked. 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": "rotate_license_key"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
noteYes
licenseYesthe license with its new key, masked

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by spelling out the consequences of this destructive operation: the license and its machines are preserved, the old key stops working immediately, and the customer is emailed the new one. It also notes the response masks the new key, which is important for an agent that must relay or store the result.

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 tight sentences: what happens, why to use it, and the confirmation requirement. The consequence (old key refused) is front-loaded, and nothing is redundant with the title or annotations.

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 tool with an output schema, the description covers the mutation's blast radius, the customer-facing side effect, the return-value masking, and the confirmation requirement. Nothing an agent needs before invoking it 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's description already explains that it accepts a license id, a full key, a key prefix, or a customer email. The prose adds no additional constraint or format detail beyond that, so the baseline of 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 ('Give a license a new key') and immediately scopes what changes and what stays: same license, same machines, old key refused, customer emailed. This clearly separates it from reveal_license_key or issue_license, which do not replace the existing key.

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?

Gives an explicit triggering condition ('For a key that leaked or was shared') and a procedural guardrail ('Confirm with the user first'). It does not name a sibling alternative or state when-not to use it, which keeps it short of a 5.

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