Skip to main content
Glama
stier1ba

LicenseSpring MCP Server

by stier1ba

Get Installation File

get_installation_file

Generate download details for installation files by providing a license key, hardware ID, and product identifier. Integrates with LicenseSpring MCP Server for streamlined license management.

Instructions

Get installation file download information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hardware_idYes
license_keyYes
productYes

Implementation Reference

  • The asynchronous handler function that performs an API GET request to fetch installation file data using the provided license_key, hardware_id, and product parameters. It 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/installation_file?${queryParams}`);
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error getting installation file: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
  • Zod-based input schema defining 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'),
    },
  • Registers the 'get_installation_file' tool on the MCP server with title, description, input schema, and inline handler function.
    server.registerTool('get_installation_file', {
      title: 'Get Installation File',
      description: 'Get installation file download information',
      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/installation_file?${queryParams}`);
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error getting installation file: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
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. 'Get installation file download information' implies a read-only operation but doesn't specify what format the download information comes in, whether it includes URLs, file sizes, checksums, or other metadata. It also doesn't mention any authentication requirements, rate limits, 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 extremely concise at just 5 words with no wasted language. It's front-loaded with the core purpose and doesn't contain any unnecessary elaboration or repetition.

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 tool with 3 required parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't compensate for the missing structured information about parameters, behavior, or return values. The agent would struggle to use this tool effectively without guessing parameter meanings and expected outputs.

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 for all 3 required parameters (hardware_id, license_key, product), the description provides no additional meaning about what these parameters represent. The description doesn't explain what hardware_id refers to, what format license_key should be in, or what product values are valid.

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 'Get installation file download information' clearly states the action (get) and resource (installation file download information), but it's somewhat vague about what exactly 'download information' entails. It doesn't distinguish this tool from potential siblings like 'get_versions' or 'get_product_details' that might also provide file-related information.

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. Given the sibling tools include various license and product information tools, there's no indication of when this specific file download information tool is appropriate versus other get_* tools.

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