Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

sdk_snippet

Read-onlyIdempotent

Generates license-validation code using the official SunLicense SDK in your chosen language, so you can add working license checks to your app.

Instructions

Code that validates a license with an official SunLicense SDK, ready for this server.

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": {
      "language": "<language>"
    },
    "name": "sdk_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesthe SDK: java also for Kotlin and Minecraft (Paper, Spigot), js for Node.js, Electron and TypeScript, dotnet for C#, lua for FiveM

Output Schema

NameRequiredDescriptionDefault
sdkYes
codeNothe validation code, ready for this server
noteYes
repoYes
installYes
usedForYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds only the hint that the snippet is pre-tailored to this server, which is modest but real added context. It says nothing about whether output is static text or dynamically generated, or what languages are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no wasted words, but the brevity comes at the cost of under-specification rather than efficiency. There is no front-loaded statement of what the tool actually does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 parameter is fully described in the schema. However, for a tool whose entire value is the produced snippet, the description never clarifies the action, the scope of languages, or when to reach for it, leaving the core behavior ambiguous.

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 single enum parameter is fully documented with language-to-platform mappings in the schema itself. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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

Purpose3/5

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

The description is a noun phrase ('Code that validates a license with an official SunLicense SDK') rather than a verb+resource statement, so it never says whether the tool generates, fetches, or returns a snippet. The subject matter (license-validation sample code) is inferable from the name and text, but the agent must guess the action. It does not distinguish itself from siblings like offline_license_file.

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

Usage Guidelines2/5

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

No when-to-use guidance, no exclusions, and no mention of any alternative among the many sibling tools. 'ready for this server' hints at a context but gives no condition for choosing this tool over, say, offline_license_file or get_license.

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