Skip to main content
Glama
stier1ba

LicenseSpring MCP Server

by stier1ba

Change Password

change_password

Update a user-based license password securely by providing the username, current password, and new password for the LicenseSpring MCP Server.

Instructions

Change password for a user-based license

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
new_passwordYes
passwordYes
usernameYes

Implementation Reference

  • The handler function that implements the core logic of the 'change_password' tool by proxying to the LicenseSpring License API.
    }, async ({ username, password, new_password }) => {
      try {
        const response = await apiClient.post('/api/v4/change_password', {
          username,
          password,
          new_password,
        });
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error changing password: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
  • The registration of the 'change_password' tool, including metadata, Zod input schema, and inline handler function.
    server.registerTool('change_password', {
      title: 'Change Password',
      description: 'Change password for a user-based license',
      inputSchema: {
        username: z.string().min(1, 'Username is required'),
        password: z.string().min(1, 'Current password is required'),
        new_password: z.string().min(1, 'New password is required'),
      },
    }, async ({ username, password, new_password }) => {
      try {
        const response = await apiClient.post('/api/v4/change_password', {
          username,
          password,
          new_password,
        });
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error changing password: ${handleApiError(error)}`,
          }],
          isError: true,
        };
      }
    });
  • TypeScript interface defining the structure of the input for the change_password tool.
    export interface ChangePasswordRequest {
      username: string;
      password: string;
      new_password: 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 states the action ('Change password') but lacks details on permissions required, whether it's reversible, rate limits, or error conditions. This is a significant gap for a mutation tool with security implications.

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, making it easy to parse quickly.

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 complexity (a password change operation with security implications), no annotations, no output schema, and 0% schema coverage, the description is inadequate. It doesn't cover behavioral aspects, parameter details, or expected outcomes, leaving critical gaps for safe and effective tool invocation.

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?

The schema description coverage is 0%, so the description must compensate, but it doesn't explain any parameters. It implies 'username', 'password', and 'new_password' through context, but doesn't add meaning beyond what the schema's property names suggest. Baseline is adjusted to 3 due to the coverage gap.

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 ('Change password') and the target ('for a user-based license'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'activate_license' or 'deactivate_license', which might involve user management but don't focus on password changes.

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 doesn't mention prerequisites (e.g., needing an active license), exclusions (e.g., not for admin accounts), or related tools in the sibling list, leaving the agent to infer usage context.

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