Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

get_license

Read-onlyIdempotent

Retrieve a single software license by ID, key prefix, or customer email, including its machines and recent license checks with the key masked.

Instructions

One license with its machines and recent license checks. The key is masked.

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>"
    },
    "name": "get_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
licenseYesthe license id, key, the start of its key, or the customer's email

Output Schema

NameRequiredDescriptionDefault
licenseYes
machinesYes
recentChecksYesthe latest license checks, newest first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds two genuinely new facts: the response bundles machines and recent license checks, and the key comes back masked rather than in clear text. Nothing contradicts the annotations.

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 short sentences, no filler, with the returned payload described before the masking caveat. Every clause carries information the reader would otherwise have to guess.

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?

An output schema exists, so return values need no explanation, and the description still usefully names what is included and flags key masking. The only real gap is routing: it does not tell an agent when to prefer this over list_licenses or reveal_license_key.

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 parameter already documents that an id, full key, key prefix, or customer email is accepted. The description adds no lookup-flexibility detail 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.

Purpose4/5

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

"One license with its machines and recent license checks" states a specific resource (a single license) plus the related data returned with it, which implicitly contrasts with list_licenses. It never names a sibling explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

The singular "one license" implies this is a single-record lookup rather than a listing, but there is no explicit when-to-use statement and no pointer to reveal_license_key or list_licenses. The masked-key note flirts with guidance but stops short of saying where to go for the unmasked value.

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