Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_policies

Read-onlyIdempotent

Retrieve license policy templates for one product or all products, including type, machine limits, and duration; null limits mean unlimited.

Instructions

List policies (license templates: type, machine limit, duration), for every product or one. maxMachines or durationDays null means unlimited.

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

Input Schema

NameRequiredDescriptionDefault
productNoproduct id, code or name; leave empty for every product

Output Schema

NameRequiredDescriptionDefault
policiesYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's burden is lighter. It adds genuinely non-obvious data semantics — 'maxMachines or durationDays null means unlimited' — that help interpret the returned records. It stops short of noting result volume, ordering, or pagination behaviour for a list operation.

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?

Two short sentences with no filler, and the resource definition is front-loaded before the filtering detail. The phrasing is compressed to the point of being slightly cryptic ('for every product or one'), but nothing is wasted.

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-optional-parameter read tool with full annotation coverage and an output schema, the description supplies what the structured fields do not: the domain meaning of a policy and the null convention for two returned fields. No significant agent need is left unaddressed.

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 single optional 'product' parameter already says 'product id, code or name; leave empty for every product'. The description's 'for every product or one' restates that meaning without adding format or matching details, so baseline 3 applies.

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 ('List policies') and immediately defines the domain term as 'license templates: type, machine limit, duration', which lets an agent recognise it without opening the schema. It also states the scope ('for every product or one'). Differentiation from siblings is only implicit through the 'list' verb versus create_policy/delete_policy.

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 only implied: an agent infers it should call this when it wants to enumerate license templates, optionally narrowed to a single product. There is no explicit when-to-use/when-not-to-use guidance and no named alternative (e.g. get/list variants for a single policy).

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