Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

create_customer

Add a license holder by email and/or name, with optional team notes, so licenses can be assigned to the correct customer.

Instructions

Add a customer (license holder) by email and/or name. issue_license also creates one from the email when needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNothe customer's name
emailNothe customer's email (an email or a name is needed)
notesNonotes for the team

Output Schema

NameRequiredDescriptionDefault
customerYesthe customer after the change

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the domain fact that a customer is a license holder, but it does not say what happens if a customer with that email already exists - notable given idempotentHint=false and the existence of merge_customers.

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?

Two short sentences with zero filler, purpose front-loaded and the cross-tool caveat second. Nothing could be cut without losing information.

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

Completeness4/5

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

With an output schema present and full schema coverage, the description only needs to convey purpose and cross-tool context, which it does. The one meaningful gap is duplicate-email behavior for a non-idempotent create in a system that has an explicit merge tool.

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?

Schema coverage is 100% and all three parameters are described in the schema itself, so baseline is 3. The description's 'by email and/or name' reinforces which fields identify the customer and that at least one is expected, but adds no format or constraint detail 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?

States a specific verb and resource ('Add a customer') and clarifies the domain meaning with '(license holder)', so the agent knows this is a person record, not a license. It does not distinguish itself from other customer-mutating siblings such as merge_customers or update_customer, but the core purpose is unambiguous.

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

Usage Guidelines4/5

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

The second sentence gives real routing context: issue_license already creates a customer from the email when needed, implying this call may be unnecessary in that flow. It stops short of an explicit when-to-use/when-not-to-use rule and says nothing about choosing between this and update_customer or merge_customers.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.