Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

deactivate_machine

DestructiveIdempotent

Frees a machine slot on a license so a customer can move to a new PC. The app on that machine must activate again.

Instructions

Free a machine slot on a license, e.g. when the customer moved to a new PC. The app on that machine has to activate again. 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": {
      "machine": "<machine>"
    },
    "name": "deactivate_machine"
  }
}

Input Schema

NameRequiredDescriptionDefault
licenseNothe license (id, key, key start or customer email); optional when machine is a machine id
machineYesthe machine's id, fingerprint or hostname, from list_machines

Output Schema

NameRequiredDescriptionDefault
noteYes
deactivatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds the real-world consequence the annotations cannot convey: the app on that machine must activate again. The instruction to confirm with the user reinforces the destructive nature with a concrete safety step. It doesn't cover licensing-seat limits or error conditions, but the key behavioral risk is disclosed.

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, front-loaded with the action and its effect, then the use case, then the safety instruction. Every sentence carries distinct information and nothing is padded.

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 single-purpose destructive tool with a full schema and an output schema, the description covers the action, the side effect, and the required user confirmation. Only edge cases (what happens if the machine is unknown or already deactivated) are left to the schema and output.

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 documents both parameters, including that machine comes from list_machines and that license is optional when a machine id is supplied. The description adds no format, matching, or ambiguity guidance beyond that, so it is baseline rather than additive.

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 ("Free a machine slot on a license") plus a concrete scenario ("customer moved to a new PC"), which is far more than a restatement of the name. It doesn't explicitly contrast with nearby tools like delete_license or list_machines, so it stops short of full sibling differentiation.

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 a clear when-to-use trigger (machine replaced by a new PC) and a procedural prerequisite ("Confirm with the user first"), which is actionable guidance for an agent. It names no alternative tool or exclusion case, so the routing guidance is contextual rather than exhaustive.

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