Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_license_ips

Read-onlyIdempotent

Lists the IP addresses using a license when its policy limits IPs, showing which hold a slot, their country, first and last seen times, and when each frees.

Instructions

List the IP addresses a license is used from when its policy limits IPs (maxIps): which hold a slot, their country, when each was first and last seen and when it frees itself.

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": {
      "license": "<license>"
    },
    "name": "list_license_ips"
  }
}

Input Schema

NameRequiredDescriptionDefault
licenseYesthe license id, key, the start of its key, or the customer's email

Output Schema

NameRequiredDescriptionDefault
ipsYes
usedYesaddresses holding a slot
maxIpsYesthe policy's IP limit; null means it doesn't limit IPs
licenseYesmasked key
releaseDaysYesdays unused after which an address frees its slot by itself

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the maxIps precondition and enumerates the semantic content of each returned entry, but says nothing about ordering, completeness, or behavior when the limit is unset.

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 no filler; the verb and resource lead. The colon-chained clause list makes it dense, and "when it frees itself" is slightly awkward phrasing, 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-parameter read tool with full annotation coverage and an output schema, the description covers purpose, precondition, and the meaning of the returned fields. The only residual gap is the undefined result when the policy has no IP limit.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself explaining that the license may be given as an id, key, key prefix, or customer email. The description adds no parameter-level meaning, 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?

The description names a specific verb and resource ("list the IP addresses a license is used from") and adds a precise qualifying condition ("when its policy limits IPs (maxIps)"), followed by an enumeration of the returned facts (slot-holding, country, first/last seen, release time). This is enough for an agent to separate it from sibling listers like list_access_rules or list_machines 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?

It gives a clear precondition for use: the license's policy must limit IPs via maxIps. What is missing is routing guidance to siblings such as release_license_ip (the obvious companion action) and any statement of what happens when no IP limit applies.

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