Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

release_license_ip

DestructiveIdempotent

Releases an IP address slot from a license so it can be used on a new server after a customer migration. Confirm with the user before making the change.

Instructions

Free an IP address's slot on a license, e.g. when the customer moved to a new server. The license then works from a new address. 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>",
      "ip": "<ip>"
    },
    "name": "release_license_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesthe address or its id, from list_license_ips
licenseYesthe license (id, key, key start or customer email)

Output Schema

NameRequiredDescriptionDefault
noteYes
afterYes
releasedYesthe address freed

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, so the safety profile is covered; the description still adds the post-condition ('The license then works from a new address') and a user-confirmation warning, which reinforces the destructive nature. It does not state reversibility or what happens if the address is already released.

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, then the motivating scenario, then the effect and the safety instruction. Nothing is redundant or 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?

With an output schema present and rich annotations, the description only needs to convey purpose, effect, and caution, which it does. Minor gaps remain around failure conditions and whether the freed slot can be reclaimed.

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 itself explains that 'ip' comes from list_license_ips and 'license' accepts id, key, key start, or customer email. The description adds no parameter detail beyond that, so the baseline 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: 'Free an IP address's slot on a license,' which is precise enough to distinguish it from sibling operations like deactivate_machine or add_access_rule. It does not explicitly name a sibling alternative, so it falls short of a 5.

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 concrete triggering scenario ('when the customer moved to a new server') and an operational precondition ('Confirm with the user first'). It stops short of stating when not to use it or which sibling handles adjacent cases such as machine deactivation.

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