Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

licensing_stats

Read-onlyIdempotent

Retrieve license counts by product and policy, active licenses, and issued or revoked licenses over 24h, 7d, or 30d ranges; omit range for today's totals.

Instructions

Licensing numbers: products, policies, licenses and active licenses; with a range (24h, 7d, 30d) also licenses issued and revoked over time and per product and policy (that report needs Lite or Standard).

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": "licensing_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoa report over this period; just today's totals when left out

Output Schema

NameRequiredDescriptionDefault
reportNothe Analytics report for the range
totalsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds genuinely non-obvious context: the plan-tier gate (Lite or Standard) on the detailed report and the behavioral difference between omitting the range (today's totals) and supplying one.

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?

A single dense sentence with the resource list front-loaded and the conditional range behavior trailing. The parenthetical plan note is the only real aside, and it carries useful information rather than filler.

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?

With an output schema present, return shape need not be described, and the single optional enum parameter is fully covered in both schema and description. The only gap is the absence of routing guidance toward or away from the analytics_* aggregation siblings, which matters for an agent choosing a stats endpoint.

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?

Schema description coverage is already 100%, so the baseline is a 3, but the description goes further by explaining the semantic consequence of leaving range empty — today's totals only — and by tying the richer per-product/per-policy output to that parameter. That is meaning the enum alone does not convey.

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 resource set — products, policies, licenses and active licenses — plus the extra time-series metrics unlocked by a range, which tells an agent this is an aggregation/counts tool rather than a listing tool like list_licenses. It stops short of naming any sibling to contrast with, so the differentiation is inferred rather than stated.

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?

Implicit guidance is present: pass a range to get issued/revoked over time, omit it for today's totals, and the time-series report requires Lite or Standard. There is no explicit statement of when to prefer this over the analytics_* siblings, so the agent must infer the choice from purpose alone.

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