Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_releases

Read-onlyIdempotent

Retrieve a product's releases, newest first, with downloadable files, whether each file carries the buyer's key or watermark, and the storage used. Read-only; requires product downloads.

Instructions

List a product's releases (versions buyers download, newest first) with their files, whether each download carries the buyer's key or mark (watermark), and the download storage used. Read-only. Needs product downloads (Standard).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product": "<product>"
    },
    "name": "list_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesthe product: code, name or id

Output Schema

NameRequiredDescriptionDefault
productYes
releasesYes
storageUsedYes
storageLimitYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context beyond them: result ordering ("newest first"), the fact that each item carries files plus per-file key/mark watermark status and download storage, and the plan-level requirement to use the tool at all.

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?

Three short sentences, front-loaded with purpose and immediately followed by return contents and then the prerequisite. "Read-only" mildly duplicates readOnlyHint, but the sentence is cheap and does not obscure anything.

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 one-parameter read tool with an output schema, the description covers purpose, ordering, return payload character, and a licensing prerequisite — enough for an agent to decide and invoke correctly. It omits pagination behavior, but with an output schema present that is a minor gap.

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?

There is a single required `product` parameter with full schema description coverage, so the schema already explains it (code, name, or id). The description reinforces that it is product-scoped but adds no accepted-format or edge-case guidance beyond the schema, which is the expected baseline here.

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 names a specific verb and resource ("List a product's releases") and defines what a release is for this domain ("versions buyers download"), which an agent can distinguish from create_release or list_products. It stops short of explicitly contrasting with a sibling, but the scope 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 Guidelines3/5

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

Usage is implied: enumerate releases for a given product. The description adds a concrete prerequisite ("Needs product downloads (Standard)"), which tells the agent when the call will be viable, but it names no alternative tool or condition for choosing a different listing endpoint.

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