Skip to main content
Glama
Labs64

Labs64/NetLicensing-MCP

netlicensing_create_product

Create a product in NetLicensing with required number and name. Optionally set version, active, description, licensing info, auto-create licensees, VAT mode, and licensee secret mode.

Instructions

Create a new product.

Args: number: Unique product number (e.g. 'P001') name: Human-readable product name version: Product version string active: Whether the product is active description: Optional product description licensing_info: Optional licensing information displayed in the shop licensee_auto_create: Auto-create licensees on first validation attempt vat_mode: GROSS or NET (leave empty to use account default) licensee_secret_mode: DISABLED, PREDEFINED, or CLIENT (leave empty for default)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYes
nameYes
versionNo1.0
activeNo
descriptionNo
licensing_infoNo
licensee_auto_createNo
vat_modeNo
licensee_secret_modeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description lacks behavioral details such as side effects, idempotency, authentication requirements, or rate limits. It only describes parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a clear purpose but uses a verbose docstring format with an 'Args' list. Could be more concise without losing clarity.

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?

Given the presence of an output schema (not required to explain returns) and 9 parameters covered, the description is fairly complete. However, it could mention typical usage context (e.g., when to set vat_mode).

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?

Schema description coverage is 0%, so the description must compensate. It provides inline parameter meanings, examples (e.g., 'P001'), and valid values (e.g., GROSS/NET for vat_mode), adding significant value beyond the bare schema.

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 clearly states 'Create a new product.' with a specific verb and resource. Among sibling create tools, it uniquely identifies product creation.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus other create tools or alternatives. The description purely lists parameters without usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Labs64/NetLicensing-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server