Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

issue_license

Issues a new license from a policy to a customer email, returns a masked key, and can email the key; counts toward the plan's license limit.

Instructions

Issue a new license from a policy to a customer. Counts toward the plan's license limit. The answer has the masked key; use reveal_license_key if the user wants the full one. With emailKey the customer gets the key by email, like a license issued in the dashboard: ask the user whether to send it.

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": {
      "policy": "<policy>",
      "customerEmail": "<customerEmail>"
    },
    "name": "issue_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyYespolicy id or name (the license template: machines, duration)
productNoproduct id, code or name, when the policy name exists in several products
emailKeyNoalso email the key to the customer, in the organization's brand (as the dashboard does); ask the user first. Default false
customerNameNothe buyer's name
customerEmailYesthe buyer's email address

Output Schema

NameRequiredDescriptionDefault
noteNo
issuedYes
emailKeyYeswhether the key was sent to the customer by email

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive, non-idempotent mutation. The description adds material facts the annotations cannot convey: the issuance consumes the plan's license limit, the returned key is masked by default, and emailing is a side effect performed in the organization's branding. It never warns that repeated calls create distinct licenses despite the non-idempotent hint, which is the one notable gap.

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?

Four short sentences, each carrying distinct information: what it does, the quota cost, the masked-return routing to a sibling, and the email side effect. The most decision-relevant constraint (quota consumption and masked key) is front-loaded with no filler.

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, the description need not describe return shape, yet it still flags the masked key, which prevents a common follow-up error. Quota impact and email side effects are covered; only permission requirements and the duplicate-issuance risk of a non-idempotent call are unaddressed for a 5-parameter mutation.

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 description coverage is 100%, so the schema already explains every parameter, including that emailKey defaults to false and requires asking the user. The description reinforces emailKey's effect ('the customer gets the key by email, like a license issued in the dashboard') but adds no new detail about policy, product, or customer fields, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource ('Issue a new license from a policy to a customer'), naming both the source template (policy) and the target (customer). That is enough for an agent to separate it from get_license, create_policy, or list_licenses without inspecting schemas.

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 explicitly routes the agent to reveal_license_key when the user wants the unmasked key, and states the conditional for emailKey ('ask the user whether to send it'). It does not spell out when not to issue (e.g., suspended policies or duplicate issuance), so it stops short of full when/when-not coverage.

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