Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_customers

Read-onlyIdempotent

List or search an organization's license holders by email, name, Discord ID, marketplace buyer ID, or key prefix, and filter results by active or blocked status.

Instructions

List or search the organization's customers (license holders).

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": "list_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNohow many to return (25 when left out)
searchNoemail or name (contains), Discord id, marketplace buyer id or the start of a key
statusNoonly customers with this status

Output Schema

NameRequiredDescriptionDefault
totalYescustomers matching, beyond those shown
customersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful domain context by defining customers as license holders, but says nothing further about pagination, filtering behavior, or return behavior beyond what the schema and output schema provide.

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 definition is a single compact sentence with the resource and operation front-loaded. There is no redundant wording or unnecessary elaboration.

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?

For a simple read-only list tool with a fully described schema, annotations, and an output schema, the description is largely sufficient. The main missing piece is explicit routing guidance versus sibling list and retrieval tools.

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 description coverage is 100%, and the three optional parameters (limit, search, status) are fully documented in the schema. The description adds no additional parameter meaning, so the baseline score of 3 is appropriate.

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 states a specific verb pair (list/search) and resource (organization's customers), and clarifies that these are license holders. It distinguishes the tool from mutation-oriented siblings such as create_customer or block_customer, but does not explicitly differentiate it from related list tools.

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 usage through 'List or search the organization's customers', which tells an agent what capability the tool provides. However, it gives no explicit when-to-use guidance, exclusions, or alternatives such as merge_customers or get_license.

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