Skip to main content
Glama
chezsmithy

Thunder Client License Manager MCP Server

by chezsmithy

thunderclient_add_license

Add Thunder Client licenses for specified email addresses using the MCP Server's API. Simplify license management with this tool to ensure access for authorized users.

Instructions

Add Thunder Client licenses for specified email addresses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailsYesArray of email addresses to add licenses for

Implementation Reference

  • Core implementation of the thunderclient_add_license tool: sends POST request to Thunder Client API to add licenses for given emails.
    async addLicense(request: AddLicenseRequest): Promise<ApiResponse> {
      const url = `${this.config.baseUrl}/api/license/add`;
      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 added licenses for ${request.emails.length} email(s)`
        };
      } catch (error) {
        return {
          success: false,
          error: `Request failed: ${error instanceof Error ? error.message : String(error)}`
        };
      }
    }
  • MCP CallToolRequestSchema handler case for thunderclient_add_license: validates input and calls the API client.
    case 'thunderclient_add_license': {
      const addRequest = (args || {}) as unknown as AddLicenseRequest;
      if (!addRequest.emails || !Array.isArray(addRequest.emails) || addRequest.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.addLicense(addRequest);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/index.ts:73-91 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema.
    {
      name: 'thunderclient_add_license',
      description: 'Add 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 add licenses for',
            minItems: 1,
          },
        },
        required: ['emails'],
      },
    },
  • TypeScript interface defining the input shape for addLicense request, matching the tool's inputSchema.
    export interface AddLicenseRequest {
      emails: string[];
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Add Thunder Client licenses', implying a write operation, but doesn't cover permissions required, whether it's idempotent, rate limits, error handling, or what happens on success (e.g., confirmation details). For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, clear sentence with no wasted words, directly stating the tool's function. It's appropriately sized and front-loaded, making it easy to understand at a glance without unnecessary elaboration.

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 is a mutation (adding licenses) with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or behavioral traits like side effects. For a tool that modifies state, more context is needed to ensure safe and correct usage, making this inadequate for its complexity.

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 'emails' parameter fully documented in the schema as an array of email addresses with a minimum of 1 item. The description adds no additional parameter semantics beyond implying the emails are for license assignment. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate or add value beyond the schema.

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 ('Add') and resource ('Thunder Client licenses') with the target ('specified email addresses'), making the purpose evident. It distinguishes from sibling tools like 'thunderclient_get_licenses' (read) and 'thunderclient_remove_license' (delete), but doesn't explicitly differentiate beyond the verb. The specificity is good but lacks explicit sibling comparison.

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_get_licenses' or 'thunderclient_remove_license'. It doesn't mention prerequisites, such as whether licenses are available or if users must exist, nor does it specify scenarios like bulk onboarding. Without such context, usage is implied but not clearly defined.

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