Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

revoke_api_key

DestructiveIdempotent

Revoke an API key to immediately stop all apps using it from validating licenses. This action is irreversible, so create a replacement key first if needed and confirm with the user.

Instructions

Revoke an API key: every app using it stops validating licenses with it at once. Can't be undone; create a new key first if the app still needs one. 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": {
      "apiKey": "<apiKey>"
    },
    "name": "revoke_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyYesthe key's id, name, or the key itself (only its start is compared)

Output Schema

NameRequiredDescriptionDefault
revokedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint; the description adds real context beyond them: immediacy across all apps, irreversibility, and the recommendation to mint a replacement first. Caller permission requirements are not covered.

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?

Three short, front-loaded sentences covering effect, irreversibility, and confirmation; minimal waste.

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 destructive single-parameter mutation with an output schema, the description covers blast radius and confirmation, which is nearly all an agent needs; permission scoping is the remaining gap.

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 schema already explains the id/name/key-prefix matching. The description adds no meaning beyond it, so baseline 3.

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?

Specific verb and resource, plus the concrete effect ('every app using it stops validating licenses with it at once'), which distinguishes it from rotation or listing tools.

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 precondition ('create a new key first if the app still needs one') and a confirmation requirement. It doesn't point to a sibling alternative, so not a 5.

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