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

Labs64/NetLicensing-MCP

by Labs64
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

netlicensing_get_product_module

Retrieve details of a specific product module by providing its identifier to manage licensing configurations.

Instructions

Get a specific product module.

Args: module_number: Module identifier

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

Input Schema

NameRequiredDescriptionDefault
module_numberYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations exist, so the description must carry the full burden. It states 'Get' indicating a read operation, but lacks details about authentication requirements, error handling, or data scope. It is adequate but not thorough.

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 two sentences: one for purpose and one for parameter. It is front-loaded, concise, and without any unnecessary words.

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?

Given the presence of an output schema (not provided but indicated), the description sufficiently covers the single retrieval operation. No additional context is needed for this straightforward tool.

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 documents the only parameter 'module_number' as 'Module identifier', adding context beyond the schema's title and type. For a single simple parameter, this is helpful but not extensive.

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 'Get a specific product module' with a verb and resource, and the name distinguishes it from siblings like netlicensing_create_product_module and netlicensing_list_product_modules.

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?

No explicit when/when-not or alternative tools are mentioned. The implication from the name and siblings is that this is for retrieving a single module by ID, but no direct guidance 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