Skip to main content
Glama
chezsmithy

Thunder Client License Manager MCP Server

by chezsmithy

thunderclient_remove_license

Remove Thunder Client licenses for specified email addresses using the API tool. Manage license assignments efficiently by inputting valid email addresses for removal.

Instructions

Remove Thunder Client licenses for specified email addresses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailsYesArray of email addresses to remove licenses for

Implementation Reference

  • Core implementation of the tool: sends POST request to Thunder Client API /api/license/remove with accountNumber and emails to remove licenses.
    async removeLicense(request: RemoveLicenseRequest): Promise<ApiResponse> {
      const url = `${this.config.baseUrl}/api/license/remove`;
      const body = {
        accountNumber: this.getAccountNumber(),
        emails: request.emails
      };
    
      try {
        const response = await fetch(url, {
          method: 'POST',
          headers: this.getHeaders('application/json'),
          body: JSON.stringify(body)
        });
    
        const data = await response.json().catch(() => ({}));
    
        if (!response.ok) {
          return {
            success: false,
            error: `HTTP ${response.status}: ${response.statusText}`,
            data
          };
        }
    
        return {
          success: true,
          data,
          message: `Successfully removed licenses for ${request.emails.length} email(s)`
        };
      } catch (error) {
        return {
          success: false,
          error: `Request failed: ${error instanceof Error ? error.message : String(error)}`
        };
      }
    }
  • MCP tool call handler: validates input, delegates to API client, and formats response.
    case 'thunderclient_remove_license': {
      const removeRequest = (args || {}) as unknown as RemoveLicenseRequest;
      if (!removeRequest.emails || !Array.isArray(removeRequest.emails) || removeRequest.emails.length === 0) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'emails array is required and must contain at least one email address'
        );
      }
    
      const result = await this.apiClient.removeLicense(removeRequest);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/index.ts:107-125 (registration)
    Registers the tool with MCP server: defines name, description, and input schema.
    {
      name: 'thunderclient_remove_license',
      description: 'Remove Thunder Client licenses for specified email addresses',
      inputSchema: {
        type: 'object',
        properties: {
          emails: {
            type: 'array',
            items: {
              type: 'string',
              format: 'email',
            },
            description: 'Array of email addresses to remove licenses for',
            minItems: 1,
          },
        },
        required: ['emails'],
      },
    },
  • Type definition for the tool input: array of email strings.
    export interface RemoveLicenseRequest {
      emails: 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 ('Remove') but doesn't clarify if this is destructive, requires admin permissions, has side effects (e.g., revoking access), or what happens on success/failure. This leaves critical behavioral traits unspecified for a mutation tool.

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 that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized, making it easy for an agent 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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like permissions, side effects, or return values, leaving significant gaps in understanding how to invoke it correctly and interpret results.

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 100%, with the parameter 'emails' fully documented in the schema as an array of email addresses. The description adds no additional semantic context beyond implying the emails are targets for license removal, so it meets the baseline of 3 without compensating for gaps.

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 ('Remove') and resource ('Thunder Client licenses') with the target ('for specified email addresses'), making the purpose unambiguous. However, it doesn't explicitly differentiate from its sibling 'thunderclient_add_license' beyond the verb, missing a direct comparison that would elevate it to a 5.

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 like 'thunderclient_add_license' or 'thunderclient_get_licenses'. It lacks context about prerequisites, such as whether licenses must exist or if this is for revoking access, leaving the agent without usage 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/chezsmithy/thunderclient-license-manager-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server