Skip to main content
Glama
stier1ba

LicenseSpring MCP Server

by stier1ba

Deactivate License

deactivate_license

Deactivate a license linked to a specific hardware ID by providing the license key, hardware ID, and product details. Ensure license management integrity and compliance.

Instructions

Deactivate a license for a specific hardware ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hardware_idYes
license_keyYes
productYes

Implementation Reference

  • The tool handler function that performs the POST request to the LicenseSpring API to deactivate the license using the provided license_key, hardware_id, and product.
    }, async ({ license_key, hardware_id, product }) => {
      try {
        const response = await apiClient.post('/api/v4/deactivate_license', {
          license_key,
          hardware_id,
          product,
        });
        
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error deactivating license: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
  • Inline Zod schema defining the input parameters for the deactivate_license tool.
    inputSchema: {
      license_key: z.string().min(1, 'License key is required'),
      hardware_id: z.string().min(1, 'Hardware ID is required'),
      product: z.string().min(1, 'Product code is required'),
    },
  • Registration of the deactivate_license tool with the MCP server, including title, description, input schema, and handler function.
    server.registerTool('deactivate_license', {
      title: 'Deactivate License',
      description: 'Deactivate a license for a specific hardware ID',
      inputSchema: {
        license_key: z.string().min(1, 'License key is required'),
        hardware_id: z.string().min(1, 'Hardware ID is required'),
        product: z.string().min(1, 'Product code is required'),
      },
    }, async ({ license_key, hardware_id, product }) => {
      try {
        const response = await apiClient.post('/api/v4/deactivate_license', {
          license_key,
          hardware_id,
          product,
        });
        
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error deactivating license: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
  • TypeScript interface defining the request structure for deactivating a license.
    export interface DeactivateLicenseRequest {
      license_key: string;
      hardware_id: string;
      product: string;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action but doesn't describe what 'deactivate' means operationally - whether it's reversible, what permissions are required, whether it affects billing, or what happens to the hardware ID. For a mutation tool with zero annotation coverage, this leaves critical behavioral questions unanswered.

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 a single, efficient sentence that gets straight to the point with no wasted words. It's appropriately sized for the tool's apparent complexity and front-loads the essential information.

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?

For a mutation tool with 3 required parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It states what the tool does at a high level but provides none of the operational details needed to use it effectively, especially given the complex licensing context suggested by the sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and 3 required parameters, the description provides no information about what 'hardware_id', 'license_key', or 'product' mean or how they should be formatted. The description doesn't compensate for the complete lack of parameter documentation in the schema, leaving all parameters semantically undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'deactivate' and the resource 'license for a specific hardware ID', making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'deactivate_offline' or explain what distinguishes deactivating a license from other license operations.

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?

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools like 'activate_license', 'deactivate_offline', and 'check_license', there's no indication of prerequisites, appropriate contexts, or when this specific deactivation method should be chosen over others.

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

Related 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/stier1ba/licensespring-mcp'

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