Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

analytics_features

Read-onlyIdempotent

Analyze product feature usage from SDK counters: see average installs per day, uses over a date range (default 30 days), and first/last seen, filtered by licensed or unlicensed installs.

Instructions

Product analytics: which of a product's features its installs use (reported by the SDK's feature counters): installs per day on average, uses in the range (default 30 days), first and last seen. Feature usage needs Lite or Standard.

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": {
      "product": "<product>"
    },
    "name": "analytics_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNodays to average over (1 to 365, cut to the plan's history); default 30
limitNohow many features (1 to 200); default 50
sourceNoall installs (default), licensed or unlicensed ones
productYesproduct id, code or name

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
linkYes
noteNo
clippedNo
productYes
featuresYesmost used first; customerSupplied.value is the feature's name as the app reported it
otherFeaturesNofeatures beyond limit
installsPerDayYesthe product's installs per day on average

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 establish read-only, idempotent, non-destructive behavior, so the description's job is additive — and it does add value by disclosing the Lite/Standard plan requirement and the default 30-day range. It stops short of explaining how truncation to the plan's history behaves in practice, but the essential constraints are present.

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 front-loads the purpose, then lists the metrics and the plan gate; almost every clause carries information. The parenthetical about SDK feature counters is slightly verbose but justifies the data's origin.

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 annotations covering the safety profile and an output schema covering return values, the description only needs to explain scope and constraints — which it does, including the plan gate the schema does not express. A brief note on how results are ordered or truncated would make it complete.

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%, so all four parameters are already documented, and the description only echoes the default 30-day window for 'days'. It adds no meaning for 'source', 'limit', or how 'product' matching works, which is acceptable given the schema baseline but not enriching.

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 verb-plus-resource ('Product analytics: which of a product's features its installs use') and enumerates the returned metrics (installs per day average, uses in range, first/last seen). It is clearly distinct from a generic summary tool, though it never explicitly names analytics_summary or analytics_breakdown as alternatives.

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 context is implied by the metric list and the plan gate ('Feature usage needs Lite or Standard'), which tells the agent a prerequisite but not when to pick this over analytics_breakdown or analytics_summary. There are no explicit when-to-use or when-not-to-use statements.

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