Skip to main content
Glama
stier1ba

LicenseSpring MCP Server

by stier1ba

Check License

check_license

Verify license status and validity by providing a license key, hardware ID, and product details. Ensures proper license management and compliance.

Instructions

Check license status and validity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hardware_idYes
license_keyYes
productYes

Implementation Reference

  • Executes the tool logic by querying the LicenseSpring API /api/v4/check_license with license_key, hardware_id, and product parameters, returns JSON response or formatted error.
    }, async ({ license_key, hardware_id, product }) => {
      try {
        const queryParams = new URLSearchParams({
          license_key,
          hardware_id,
          product,
        });
        const response = await apiClient.get(`/api/v4/check_license?${queryParams}`);
        
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error checking license: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
  • Zod schema for input validation in the tool registration.
    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'),
    },
  • Registers the 'check_license' tool with MCP server, including title, description, input schema, and handler function.
    server.registerTool('check_license', {
      title: 'Check License',
      description: 'Check license status and validity',
      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/check_license?${queryParams}`);
        
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error checking license: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
  • TypeScript interface defining the request parameters for check_license.
    export interface CheckLicenseRequest {
      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 the full burden of behavioral disclosure. It indicates a read operation ('check'), but does not specify if it requires authentication, rate limits, or what happens on invalid inputs. It lacks details on return values or error handling, which is insufficient for a tool with no structured behavioral hints.

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 extremely concise with a single phrase, 'Check license status and validity', which is front-loaded and wastes no words. However, this conciseness comes at the cost of completeness, as it omits necessary details for effective tool use.

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 output schema, no annotations), the description is incomplete. It does not explain parameters, return values, or behavioral traits, making it inadequate for an agent to reliably invoke the tool without additional context or trial-and-error.

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?

Schema description coverage is 0%, so the description must compensate by explaining parameters. It does not mention any parameters (hardware_id, license_key, product) or their purposes, leaving them undocumented. This fails to add meaning beyond the bare schema, resulting in poor parameter guidance.

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

Purpose3/5

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

The description 'Check license status and validity' states the verb ('check') and resource ('license'), but it is vague as it does not specify what aspects of status or validity are checked (e.g., expiration, features, activation). It distinguishes from siblings like 'activate_license' by implying a read operation, but lacks specificity.

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 explicit guidance on when to use this tool versus alternatives, such as 'activate_license' or 'deactivate_license'. It implies usage for verification purposes, but does not mention prerequisites, context, or exclusions, leaving the agent to infer based on tool names alone.

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