Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

create_api_key

Generate an API key for an app to validate licenses. The key is shown once; store it as a secret in environment variables or config, never in source control.

Instructions

Create an API key (slk_…) for an app to validate licenses with. The key is shown once, here; tell the user to store it as a secret (an environment variable or config file), never in source control.

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

Input Schema

NameRequiredDescriptionDefault
nameYeswhat the key is for, e.g. 'Paper plugin' or 'CI'

Output Schema

NameRequiredDescriptionDefault
idYes
keyYesthe full API key, shown once
nameYes
noteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already disclose the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds genuinely new behavior: the secret is displayed exactly once at creation and must be stored outside source control. It leaves out what happens on repeat calls with the same name and whether the key can ever be retrieved again, which matters given idempotentHint=false.

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 tight sentences: the capability first, then the critical handling instruction. Nothing is redundant and the one-time-visibility warning is placed where an agent will act on it immediately after the call.

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 prose, and for a single-parameter create tool the definition covers what is created, what it is for, and the security handling that is the main failure mode. The remaining unknowns (name uniqueness, re-retrieval) are minor for this complexity level.

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?

With one parameter at 100% schema coverage, the schema already explains that name is "what the key is for" with examples. The description adds no further semantics for name, which is acceptable at this coverage level rather than a gap.

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?

States a specific verb and resource ("Create an API key") plus the key's prefix and its purpose ("for an app to validate licenses with"), which separates it from revoke_api_key and list_api_keys by implication. It stops short of explicitly naming a sibling or stating the contrast, so it lands just below the top band.

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?

Usage is only implied: an agent can infer this is the tool for minting a new app key, but the description gives no explicit when-to-use framing, no prerequisites (plan limits, permission scope, whether a name must be unique), and no pointer to revoke/rotate for the lifecycle counterpart.

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