Skip to main content
Glama
stier1ba

LicenseSpring MCP Server

by stier1ba

Activate License Offline

activate_offline

Activate software licenses offline by providing a license key, hardware ID, and product code for secure access without an active internet connection.

Instructions

Activate a license for offline use with hardware ID and product code

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hardware_idYes
license_keyYes
productYes
quantityNo

Implementation Reference

  • Executes the activate_offline tool by posting license activation data to the LicenseSpring API endpoint /api/v4/activate_offline and returns the JSON response or formatted error.
    }, async ({ license_key, hardware_id, product, quantity }) => {
      try {
        const requestData = {
          license_key,
          hardware_id,
          product,
          quantity,
        };
        const response = await apiClient.post('/api/v4/activate_offline', requestData);
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error activating license offline: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
  • Zod validation schema defining required inputs for the activate_offline tool: license_key, hardware_id, product (required strings), quantity (optional number default 1, min 1).
    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'),
      quantity: z.number().min(1).optional().default(1),
    },
  • Registers the activate_offline MCP tool on the server with provided title, description, schema, and handler function.
    server.registerTool('activate_offline', {
  • TypeScript interface defining the structure of ActivateOfflineRequest matching the tool's input parameters.
    export interface ActivateOfflineRequest {
      license_key: string;
      hardware_id: string;
      product: string;
      quantity?: number;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose whether this is a mutating operation, what permissions are required, what happens on success/failure, rate limits, or side effects. For a license activation tool with zero annotation coverage, this is insufficient.

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?

Single sentence that efficiently conveys the core purpose with zero wasted words. The description is appropriately sized and front-loaded with 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 license activation tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, error handling, or important behavioral aspects. The context signals indicate significant complexity that the description doesn't adequately address.

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 description coverage is 0%, so the description must compensate. It mentions 'hardware ID and product code' which maps to 2 of the 4 parameters (hardware_id and product), but doesn't explain 'license_key' or 'quantity'. The description adds some meaning but doesn't fully compensate for the schema coverage gap, especially for the required 'license_key' parameter.

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 action ('activate') and resource ('license for offline use') with specific parameters mentioned (hardware ID and product code). It distinguishes from siblings like 'activate_license' by specifying 'offline use', but doesn't fully explain how it differs from 'deactivate_offline' or other license-related tools.

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 explicit guidance on when to use this tool versus alternatives like 'activate_license' or 'deactivate_offline'. The description implies it's for offline activation but doesn't specify prerequisites, error conditions, or when to choose this over other license management tools in the sibling list.

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