Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

revoke_license

DestructiveIdempotent

Permanently revoke a software license by license ID, key, or customer email. The customer's app returns REVOKED within seconds and the action cannot be undone, so confirm first.

Instructions

Revoke a license for good: the customer's app answers REVOKED within seconds and it 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": {
      "license": "<license>"
    },
    "name": "revoke_license"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
licenseYesthe license after the change

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is partly covered. The description adds value beyond that: it discloses the propagation speed ('answers REVOKED within seconds') and the permanence ('can't be undone'), plus a human-confirmation requirement, none of which appear in the annotations.

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 destructive consequence front-loaded before the confirmation instruction. Nothing is padded, though the colon construction packs the effect and permanence into one long clause that could be split for scannability.

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?

An output schema exists, so return values need not be explained, and the single required parameter is fully documented in the schema. The description covers consequence, permanence, timing, and the confirmation prerequisite — enough for correct invocation, with only the revoke-vs-delete distinction left unaddressed.

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 description coverage is 100% and the single 'license' parameter already documents that it accepts an id, key, key prefix, or customer email. The description adds no further meaning about that parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Revoke a license') and immediately describes the observable outcome: the customer's app answers REVOKED. An agent knows exactly what operation this performs. It does not, however, distinguish itself from close siblings like delete_license, suspend_license, or reinstate_license, which are conceptually adjacent.

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

Usage Guidelines3/5

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

The description supplies one strong procedural guideline — 'Confirm with the user first' — which is genuinely useful for a destructive operation. But it gives no guidance on when to choose revoke over delete_license or suspend_license, so the agent must infer the alternative from sibling names alone.

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