Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

analytics_summary

Read-onlyIdempotent

Summarizes product install analytics: active installs in the last hour, licensed vs unlicensed counts, installs today and over 30 days, and per-day distinct installs for a chosen day range.

Instructions

Product analytics: active installs (reported in the last hour), licensed vs unlicensed, installs today and in 30 days, per product or for every product, with a link to the product's Analytics tab. With days, also distinct installs per day.

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

Input Schema

NameRequiredDescriptionDefault
daysNoalso list installs per day over this many days (1 to 365, cut to the plan's history)
productNoproduct id, code or name; empty = every product's active installs

Output Schema

NameRequiredDescriptionDefault
noteNo
planNo
clippedNothe days asked for go back further than the plan's history, so they were cut
productsYes
installsByDayNodistinct installs per UTC day, oldest first (with days)
activeInstallsYesinstalls of these products that reported in the last 60 minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the read-only and idempotent hints provided in annotations, the description adds valuable behavioral context by noting that it includes 'a link to the product's Analytics tab.' This describes a specific user experience feature of the returned data, not just the data itself.

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?

The definition is a highly dense, single paragraph that front-loads the primary function ('Product analytics'). Every phrase contributes directly to defining the tool's capability and scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of generating a summary report, the definition is complete. It addresses the metrics, the scope of the scope (per product vs. all), and provides the behavioral context of an embedded link, leaving no major gaps for an agent to correctly invoke it.

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?

The input schema has 100% description coverage. The description clarifies the functional intent of the parameters—namely that an empty 'product' string encompasses 'every product'—which adds meaningful context, though it does not compensate for a large schema gap as none exists.

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 provides a specific function ('Product analytics') and details the precise metrics included (active installs, licensed vs unlicensed, installs today/30 days, distinct installs per day). This makes it easy for the AI to classify the tool's role.

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?

The description clearly dictates the scope of the output, specifying whether the user wants data 'per product or for every product.' This acts as guidance on how to utilize the tool's scope.

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