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

Labs64/NetLicensing-MCP

by Labs64
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

netlicensing_delete_license

Permanently delete a license by its license number, with an option to force cascade and remove dependent objects.

Instructions

Delete a license permanently.

Args: license_number: License to delete force_cascade: Force deletion even if dependencies exist

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": {
      "license_number": "<license_number>"
    },
    "name": "netlicensing_delete_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
license_numberYes
force_cascadeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Without annotations, the description carries the burden. It states the permanent nature and mentions the force_cascade parameter, but lacks details on authorization needs or error conditions.

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 with no wasted words, front-loading the purpose and clearly listing arguments in a structured format.

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?

For a simple delete operation with two parameters and an output schema, the description covers the essential behavior and options, though it omits details about return values or failure modes.

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 description must compensate. It adds brief explanations for each parameter ('License to delete', 'Force deletion even if dependencies exist'), which adds value but could be more detailed.

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 'Delete a license permanently' which specifies the verb (delete) and resource (license), distinguishing it from sibling tools like delete_bundle or delete_licensee.

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 alternatives, such as when to favor other deletion tools. No prerequisites or exclusions are mentioned.

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