Skip to main content
Glama
iaptic

Iaptic MCP Server

Official
by iaptic

customer_get

Retrieve complete customer profile including purchase history, active and expired subscriptions, renewal status, and introductory period details using a customer ID.

Instructions

Get detailed information about a specific customer.

  • Returns complete customer profile including:

    • Application username

    • Purchase history

    • Active and expired subscriptions

    • Last purchase details

    • Subscription renewal status

    • Trial and introductory period information

  • Required: customerId parameter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesUnique identifier of the customer

Implementation Reference

  • The handler function for customer_get. Calls this.api.getCustomer(args.customerId) and returns the result as JSON text.
    case 'customer_get':
      const customer = await this.api.getCustomer(args.customerId);
      return {
        content: [{
          type: "text",
          text: JSON.stringify(customer, null, 2)
        }]
      };
  • Input schema for customer_get tool. Defines customerId (required string) and optionally appName when using master key.
    inputSchema: {
      type: "object",
      properties: {
        customerId: { 
          type: "string", 
          description: "Unique identifier of the customer" 
        },
        ...(appNameRequired ? {
          appName: {
            type: "string",
            description: "Name of the app to fetch data from. Required when using master key."
          }
        } : {})
      },
      required: appNameRequired ? ["customerId", "appName"] : ["customerId"]
    }
  • Registration of the customer_get tool with name, description, and inputSchema in the getTools() method of CustomerTools class.
          {
            name: "customer_get",
            description: `Get detailed information about a specific customer.
    - Returns complete customer profile including:
      - Application username
      - Purchase history
      - Active and expired subscriptions
      - Last purchase details
      - Subscription renewal status
      - Trial and introductory period information
    - Required: customerId parameter${appNameRequired ? '\n- Requires appName parameter when using master key' : ''}`,
            inputSchema: {
              type: "object",
              properties: {
                customerId: { 
                  type: "string", 
                  description: "Unique identifier of the customer" 
                },
                ...(appNameRequired ? {
                  appName: {
                    type: "string",
                    description: "Name of the app to fetch data from. Required when using master key."
                  }
                } : {})
              },
              required: appNameRequired ? ["customerId", "appName"] : ["customerId"]
            }
          },
  • The API helper method getCustomer() that makes the actual HTTP GET request to /customers/:customerId endpoint.
    async getCustomer(customerId: string, params?: { appName?: string }) {
      const response = await this.client.get(`/customers/${customerId}`, { params });
      return response.data;
    }
  • src/server.ts:90-91 (registration)
    Server routing: tools starting with 'customer_' are routed to CustomerTools.handleTool(), which handles customer_get via switch-case.
    if (name.startsWith('customer_')) {
      return await this.tools.customers.handleTool(name, args);
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It lists return fields but does not disclose whether the operation is read-only, what happens if customerId is invalid (e.g., 404 error), or any rate limits. The description lacks important behavioral context beyond the output structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose sentence followed by bullet points listing return fields. It is somewhat lengthy but each bullet adds value. Front-loads the main action. Could be slightly trimmed, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without an output schema, the description partially compensates by listing expected fields. However, it lacks details on error conditions, required permissions, or response format (e.g., status codes). For a simple get-by-ID tool, it is adequate but not fully complete, especially given the absence of annotations.

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 input schema fully describes the single parameter (customerId) with 100% coverage. The description redundantly states 'Required: customerId parameter' but adds no new semantic meaning beyond the schema. Baseline 3 is appropriate as the schema already does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get detailed information about a specific customer.' It lists specific return fields, making the function unambiguous. Sibling tools like customer_list or customer_add_purchase have distinct purposes, so this tool is well-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when detailed info on one customer is needed but does not explicitly state when to avoid using it or mention alternatives. For example, it doesn't say 'Use customer_list for summaries' or 'Do not use for batch operations.' No comparison to siblings is provided.

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

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/iaptic/mcp-server-iaptic'

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