Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

create_release

Destructive

Creates a product release on SunLicense by uploading built files and publishing it, or returns the CLI command to upload and publish later. Drafts are supported; published versions are refused.

Instructions

Create a release of a product, the version buyers download (Standard). With files (local paths of the built files), it uploads them straight to SunLicense (never through the model), waits for SunLicense's check and publishes the release unless draft is true; buyers can download it at once, so confirm with the user first. Without files it creates a draft and returns the sunlicense releases create command that uploads the files into it and publishes it. A draft of the same version gets the files; a published version is refused.

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": {
      "product": "<product>",
      "version": "<version>"
    },
    "name": "create_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftNoupload without publishing: buyers don't see it until it is published
filesNolocal paths of the built files buyers download (local CLI server only); read and uploaded to SunLicense, never shown to the model
notesNorelease notes (Markdown)
titleNoa short title buyers see
productYesthe product: code, name or id
versionYesthe release's version, e.g. 1.4.0

Output Schema

NameRequiredDescriptionDefault
noteYes
filesYes
statusYes
productYes
versionYes
publishedYes
releaseIdYes
downloadsUrlYes
uploadCommandNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: files go straight to SunLicense and never through the model, the tool waits for SunLicense's check, publishing makes files immediately downloadable, and the user should confirm first. It also explains the no-files draft flow and same-version collision behavior, which is exactly the operational context needed for a destructive mutation.

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?

The description is dense but front-loaded, starting with purpose and then explaining the important branches. The second sentence is long and repeats some schema wording, but there is no obvious filler.

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?

Given the tool is a destructive mutation with annotations and an output schema, the description supplies all key operational context: publish visibility, user confirmation, file upload path, draft fallback, returned CLI command, and collision behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds conditional meaning for files, draft, and version beyond the schema: files present triggers upload/publish unless draft is true, files absent creates a draft and returns a CLI command, and a published version is refused.

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: 'Create a release of a product, the version buyers download (Standard).' The with-files and without-files branches distinguish it from generic product creation siblings.

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 clear conditional usage: with files it uploads and publishes unless draft is true; without files it creates a draft and returns a CLI command. It warns to confirm with the user before publishing and states a published version is refused, though it does not name sibling alternatives.

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