Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

validation_stats

Read-onlyIdempotent

Reports license-check activity and trends: active machines, activations, today's checks, plus valid/rejected checks, response codes, busiest licenses, and countries over 24h, 7d, or 30d.

Instructions

License-check numbers: active machines, activations and checks today; with a range (24h, 7d, 30d) also valid and rejected checks over time, answers by code, the busiest licenses (keys masked) and countries.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
todayYes
reportNothe Analytics report for the range (keys masked)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world call, so the safety bar is low. The description adds one genuinely useful behavioral note, that license keys are masked in the busiest-licenses output, but says nothing about cost, aggregation granularity, or whether 'answers by code' is truncated.

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 dense sentence with no filler, and the primary metrics come first with the ranged additions after. It verges on a run-on list, but every clause names a distinct output rather than padding.

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, the description need not explain return shapes, and annotations cover the safety profile. The only real gap is the lack of differentiation from the near-named sibling licensing_stats, which an agent would need in order to choose correctly.

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 coverage is 100% and the enum already documents 24h/7d/30d plus the default behavior, so the baseline is 3. The description partly restates the schema's default-by-omission rule while adding that a range unlocks the time-series and breakdown sections, which is a modest gain in meaning.

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 the resource (license-check numbers) and enumerates the concrete outputs: active machines, activations, checks today, valid/rejected checks over time, answers by code, busiest licenses, countries. That is far more specific than a restated title. It does not, however, distinguish itself from the sibling licensing_stats, so an agent cannot tell from the text which of the two stats tools to pick.

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?

There is an implicit usage rule in 'just today's totals when left out,' which tells the agent what happens with no range. Beyond that there is no explicit when-to-use or when-not-to-use guidance, and no routing to licensing_stats or analytics_summary, which look like overlapping reads.

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