Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_products

Read-onlyIdempotent

Lists an organization's products so AI assistants can identify items before issuing, suspending, or managing license keys.

Instructions

List the organization's products.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no note on result size, ordering, pagination, or whether trashed/archived products are included, which is notable given a sibling list_trash exists.

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?

A single front-loaded sentence with zero filler or redundancy. It is not under-specified in the way of a bare tool name, but it could have carried one more clause of routing or scope information at no cost to brevity.

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?

With an output schema present, the description needn't explain return values, and zero parameters means nothing to document. However, for a listing tool in a large family of list_* siblings, the absence of any routing or scope statement leaves a real gap an agent would notice when choosing between it and list_trash or get_license.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema-completeness baseline of 4 applies. The description's mention of 'the organization's' at least signals the implicit tenant scope, which is meaningful for a parameterless listing call.

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 (List) and resource (the organization's products), so the agent knows exactly what it retrieves. It does not distinguish itself from neighboring read tools like list_licenses or list_releases, nor mention how it differs from create_product/delete_product, but the resource 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 Guidelines2/5

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

No guidance on when to call this versus alternatives, no prerequisites, and no mention of scoping (e.g., whether results are paginated or filtered by default). The agent must infer from the name alone that this is the ordinary way to enumerate products.

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