Skip to main content
Glama
stier1ba

LicenseSpring MCP Server

by stier1ba

Get SSO URL

get_sso_url

Generate a Single Sign-On URL for customer portal access using product details and customer account code, enabling quick authentication for license management.

Instructions

Get Single Sign-On URL for customer portal access

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_account_codeYes
productYes
response_typeNotoken

Implementation Reference

  • The main handler function implementing the get_sso_url tool. It accepts product, customer_account_code, and optional response_type, constructs query parameters, calls the LicenseSpring API endpoint /api/v4/sso_url/, returns the JSON response or error message.
    }, async ({ product, customer_account_code, response_type }) => {
      try {
        const queryParams = new URLSearchParams({
          product,
          customer_account_code,
          response_type,
        });
        const response = await apiClient.get(`/api/v4/sso_url/?${queryParams}`);
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error getting SSO URL: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
  • Zod input schema validation for the get_sso_url tool parameters.
    inputSchema: {
      product: z.string().min(1, 'Product code is required'),
      customer_account_code: z.string().min(1, 'Customer account code is required'),
      response_type: z.string().optional().default('token'),
    },
  • Registration of the get_sso_url tool on the MCP server, including title, description, input schema, and inline handler function.
    server.registerTool('get_sso_url', {
      title: 'Get SSO URL',
      description: 'Get Single Sign-On URL for customer portal access',
      inputSchema: {
        product: z.string().min(1, 'Product code is required'),
        customer_account_code: z.string().min(1, 'Customer account code is required'),
        response_type: z.string().optional().default('token'),
      },
    }, async ({ product, customer_account_code, response_type }) => {
      try {
        const queryParams = new URLSearchParams({
          product,
          customer_account_code,
          response_type,
        });
        const response = await apiClient.get(`/api/v4/sso_url/?${queryParams}`);
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error getting SSO URL: ${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 but only states what the tool does, not how it behaves. It lacks details on authentication needs, rate limits, response format, or potential side effects, which are critical for a tool that likely generates access URLs.

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 with no wasted words. It's front-loaded with the core purpose and appropriately sized for the tool's apparent complexity.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, parameter meanings, or return values, making it inadequate for a tool with 3 parameters that likely involves authentication flows.

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 but adds no parameter information. It doesn't explain what 'customer_account_code', 'product', or 'response_type' mean, their formats, or how they affect the SSO URL generation, leaving parameters largely undocumented.

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 'Get' and the resource 'Single Sign-On URL', specifying it's for 'customer portal access'. This provides a specific purpose, though it doesn't explicitly differentiate from sibling tools like 'get_product_details' or 'get_versions' that also retrieve 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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the purpose alone without explicit direction.

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