Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

test_validate

Validate a license key through the validation API with an API key and view the result; a new fingerprint consumes a machine slot until deactivated.

Instructions

Validate a license key the way the user's app does (the validation API, with an API key) and show the answer. A fingerprint the license hasn't seen takes a machine slot, like a first run, and keeps it for good: free it afterwards with deactivate_machine. Needs SUNLICENSE_API_KEY (an slk_ API key) in the MCP server's environment.

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": {
      "licenseKey": "<licenseKey>",
      "fingerprint": "<fingerprint>"
    },
    "name": "test_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
licenseKeyYesthe full license key
fingerprintYesa machine id; a new one takes a machine slot, like the app's first run

Output Schema

NameRequiredDescriptionDefault
keyYesthe key that was checked, masked
codeYes
validYes
detailNo
machinesYesmachines in use and the policy's limit (null: unlimited)
expiresAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations it discloses the two facts an agent would otherwise not know: the call is not a pure read because a new fingerprint permanently consumes a machine slot, and the server requires SUNLICENSE_API_KEY (an slk_ key) in its environment. That matches readOnlyHint=false and idempotentHint=false without contradicting them, since the side effect is additive and the description supplies the remediation path.

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?

Two sentences, front-loaded with the purpose, then the side effect, then the prerequisite. Nothing is repeated or padded, and the most dangerous detail (permanent slot consumption) is not buried.

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?

An output schema exists, so return values need no explanation, and the description covers the remaining unknowns for a non-idempotent validation call: the auth prerequisite, the persistent side effect, and the cleanup tool. Nothing needed for a correct invocation is missing.

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 both parameter descriptions already say what the description says (full license key; a new machine id takes a slot like first run). The description adds no syntax, format, or edge-case meaning beyond the schema, so the baseline of 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?

The description names a specific verb and resource ("Validate a license key") and pins the semantics precisely as "the way the user's app does (the validation API, with an API key)", which separates it from catalog-inspection siblings like get_license or validate_automation. It stops short of naming a sibling explicitly, so a 4 rather than a top mark.

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?

It states the usage context (simulating an app-side check with the real validation API) and points at the follow-up path: "free it afterwards with deactivate_machine". No explicit when-not-to-use clause or contrast against validate_automation/get_license is given, so it is strong but not complete routing guidance.

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