Skip to main content
Glama
Labs64

Labs64/NetLicensing-MCP

netlicensing_create_transaction

Create a new transaction by specifying status (CANCELLED, CLOSED, PENDING) and source (SHOP or AUTO). Optionally set licensee, custom number, name, active flag, dates, and payment method.

Instructions

Create a new transaction.

Args: status: CANCELLED | CLOSED | PENDING source: Transaction source — SHOP or AUTO (default SHOP) licensee_number: Optional — associated licensee number: Optional custom transaction number (auto-generated if empty) name: Optional human-readable transaction name active: Whether the transaction is active date_created: Optional ISO 8601 creation timestamp date_closed: Optional ISO 8601 close timestamp payment_method: Optional payment method number

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
sourceNoSHOP
licensee_numberNo
numberNo
nameNo
activeNo
date_createdNo
date_closedNo
payment_methodNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

No annotations exist, and the description fails to disclose behavioral traits such as side effects, auth requirements, rate limits, or what happens upon creation. The tool's behavior beyond parameter values is completely opaque.

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?

The description is concise, using a bullet list format with no redundant information. Every sentence adds value for parameter understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the parameter details are covered, the description lacks broader context: no usage guidance, no behavioral traits, and no mention of the output despite an existing output schema. The tool's role in the transaction lifecycle is not explained.

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?

The description adds meaning to all 9 parameters beyond the schema (e.g., enum values for status, explanation of source), compensating for the 0% schema description coverage. However, it does not describe the return value or output structure.

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 explicitly states 'Create a new transaction.' with a clear verb and resource, and it is distinguished from sibling tools like netlicensing_list_transactions and netlicensing_update_transaction.

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 is provided on when to use this tool versus alternatives (e.g., update_transaction for modifications). The description only 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