Skip to main content
Glama
Sign In
Labs64/NetLicensing-MCP

Labs64/NetLicensing-MCP

by Labs64
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

netlicensing_obtain_bundle

Creates licenses from all license templates in a bundle for a specified licensee using the bundle number and licensee number.

Instructions

Obtain a bundle for a customer — creates licenses from all license templates included in the bundle for the specified licensee.

Args: bundle_number: Bundle to obtain licensee_number: Customer (licensee) who receives the licenses

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": {
      "bundle_number": "<bundle_number>",
      "licensee_number": "<licensee_number>"
    },
    "name": "netlicensing_obtain_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundle_numberYes
licensee_numberYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, so the description must fully disclose behavioral traits. It mentions 'creates licenses' indicating a write operation, but lacks details on side effects (e.g., overwriting existing licenses), required permissions, error handling, or idempotency. Minimal disclosure overall.

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

Conciseness4/5

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

The description is concise with a clear sentence followed by an 'Args:' section listing parameters. No redundant information, though the parameter descriptions are minimal.

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?

Given low complexity (2 required params, no enums) and existence of an output schema, the description covers basic purpose but omits important context like error scenarios, prerequisites (e.g., existence of bundle and licensee), and effects on existing licenses. Incomplete for practical use.

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 coverage is 0%, so the description must add meaning. It provides brief descriptions: 'Bundle to obtain' and 'Customer (licensee) who receives the licenses.' This adds some context but is not rich enough to fully explain the parameters beyond their names.

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 'Obtain a bundle for a customer — creates licenses from all license templates included in the bundle for the specified licensee.' This provides a specific verb (obtain), resource (bundle), and action (creates licenses), distinguishing it from sibling tools like netlicensing_create_license or netlicensing_get_bundle.

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?

The description implies usage for bulk license creation via a bundle but does not explicitly state when to use this tool versus alternatives like netlicensing_create_license. No guidance on when not to use it is provided.

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

Deploy Server

Other Tools