Skip to main content
Glama
stier1ba

LicenseSpring MCP Server

by stier1ba

Get Software Versions

get_versions

Retrieve available software versions for a product using license key, hardware ID, and product details. Integrates with LicenseSpring MCP Server for streamlined license management.

Instructions

Get available software versions for a product

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hardware_idYes
license_keyYes
productYes

Implementation Reference

  • The handler function for the 'get_versions' tool. It takes license_key, hardware_id, and product as input, makes a GET request to the LicenseSpring API /api/v4/versions endpoint with these as query parameters, and returns the JSON response or an error message.
    }, async ({ license_key, hardware_id, product }) => {
      try {
        const queryParams = new URLSearchParams({
          license_key,
          hardware_id,
          product,
        });
        const response = await apiClient.get(`/api/v4/versions?${queryParams}`);
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error getting versions: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
  • The input schema for the 'get_versions' tool defined using Zod (z), validating the required string parameters: license_key, hardware_id, and product.
    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'),
    },
  • The registration of the 'get_versions' MCP tool on the server, including title, description, input schema, and inline handler function.
    server.registerTool('get_versions', {
      title: 'Get Software Versions',
      description: 'Get available software versions for a product',
      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 queryParams = new URLSearchParams({
          license_key,
          hardware_id,
          product,
        });
        const response = await apiClient.get(`/api/v4/versions?${queryParams}`);
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error getting versions: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves versions but does not describe what 'available' means (e.g., all versions, only compatible ones), whether it requires authentication (implied by license_key but not stated), or any rate limits or error conditions. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence with no unnecessary words. It is front-loaded with the core purpose, making it easy to scan and understand quickly. Every part of the sentence earns its place by conveying essential information without redundancy.

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 the tool's complexity (3 required parameters, no annotations, no output schema), the description is incomplete. It does not explain the parameters' meanings, the tool's behavior beyond retrieval, or what the output looks like (e.g., list of versions, compatibility info). For a tool that likely interacts with licensing or product systems, more context is needed to use it effectively.

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?

The input schema has 3 required parameters with 0% description coverage, so the schema provides no semantic information. The description does not explain what 'hardware_id', 'license_key', or 'product' represent or how they affect the output. For example, it does not clarify if 'product' refers to a software name or ID, or if 'hardware_id' is needed for compatibility checks. This fails to compensate for the low schema coverage.

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 tool's purpose as 'Get available software versions for a product', which includes a specific verb ('Get') and resource ('software versions'). However, it does not explicitly differentiate from sibling tools like 'get_product_details' or 'get_installation_file', which might also retrieve product-related information, leaving some ambiguity about its unique role.

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. It does not mention prerequisites, such as needing a license key or hardware ID, or specify scenarios where this tool is preferred over siblings like 'get_product_details'. This lack of context makes it difficult for an agent to decide when to invoke it.

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