Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_licenses

Read-onlyIdempotent

List and search licenses newest first, filtering by status, product, customer email, name, or key prefix; key values remain masked.

Instructions

List or search licenses (newest first). Keys are masked; use reveal_license_key for one full key.

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_licenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNohow many to return (25 when left out)
searchNothe start of a key, a customer email or a name
statusNoonly licenses with this status
productNoonly this product (id, code or name)

Output Schema

NameRequiredDescriptionDefault
shownYes
licensesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds two things annotations cannot convey: results come newest-first, and key fields are masked in the response, which is important for an agent deciding whether it has enough data.

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. The core operation and ordering come first, followed by the masking caveat and the sibling hand-off.

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?

An output schema exists, so return-value explanation is not required, and the description covers the two non-obvious response traits (ordering, masking). Nothing critical is missing for a four-parameter, zero-required list 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 description coverage is 100%, so all four parameters (limit, search, status, product) are already documented, including the enum values and defaults. The description mentions searching but adds no syntax or matching-rule detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb ('List or search') and resource ('licenses'), plus scope details (newest-first ordering) and an explicit hand-off to reveal_license_key for full keys. An agent can distinguish this from get_license and reveal_license_key without opening a schema.

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?

Explicitly routes the full-key use case to reveal_license_key, which is the main ambiguous alternative. It does not contrast against list_customers or get_license, but the context it gives is clear enough to select correctly.

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