Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

create_product

Create a product record for an app or plugin to attach a licensing policy and manage its keys; each product counts toward the plan limit.

Instructions

Create a product (the app or plugin being licensed). Counts toward the plan's product limit. Then create a policy for it with create_policy.

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_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesthe product's name, e.g. 'Acme Editor'
descriptionNoone line about it, for the team

Output Schema

NameRequiredDescriptionDefault
createdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, so the safety profile is covered. The description adds genuinely new behavior beyond that: the call consumes a slot against the plan's product limit, which is a quota consequence the agent would otherwise miss. It stops short of saying what happens on a duplicate name or a limit-exceeded error.

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 compact sentences with zero filler; the identity of the resource is front-loaded and the quota and follow-up notes come after. Every clause carries information an agent needs.

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 not be explained, and the annotations plus the quota note cover the important behavioral surface for a simple two-parameter write. The only gap is failure behavior for duplicate names or hitting the product limit.

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 both parameters are already documented with examples in the schema. The description restates only the product concept and never touches the optional `description` field, so it adds no meaning beyond the structured data.

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?

States a specific verb and resource and then defines the resource domain-specifically as 'the app or plugin being licensed', which an agent cannot infer from the name alone. The resource is clearly distinct from sibling creators such as create_policy, create_customer, and create_release.

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

Usage Guidelines5/5

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

Provides an explicit sequencing rule: create the product first, then 'create a policy for it with create_policy'. That names the alternative/next tool and the condition that selects it, leaving little to inference.

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