Skip to main content
Glama

KrystalView Analytics

by io.github.KrystalView

Get Site Stats

get_site_stats
Read-onlyIdempotent

Get aggregate site metrics including all sessions, likely human sessions, likely bot/crawler sessions, duration, friction, rage clicks, daily counts, device mix, and top pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback period in days.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesAggregate site analytics metrics with traffic_quality fields for all, likely human, and likely bot/crawler sessions, plus trend series, device mix, top pages, and friction distribution.
metaYesSite and rate-limit metadata for the current MCP call.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to reiterate safety. The description adds value by listing return metrics, but lacks details like rate limits or response size.

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?

The description is a single sentence that is efficient and informative, though slightly lengthy due to listing many metrics.

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

Completeness3/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 detail return structure, but it lacks context on prerequisites or usage examples.

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 description adds no new meaning beyond the schema's description of the 'days' parameter.

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 clearly states the tool returns 'aggregate site metrics' and lists specific metrics, distinguishing it from sibling tools that focus on campaigns, funnels, or detailed session data.

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?

The description implies this is for overall site stats but does not explicitly state when to use it versus alternatives like get_sessions or get_live_visitors.

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

All KrystalView Analytics toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct analytics dimension (anomalies, campaigns, errors, funnels, live visitors, notifications, scroll depth, sessions, site stats) with clear boundaries. Even overlapping concepts (sessions list vs detail vs live) are separated by distinct functionality.

Naming Consistency5/5

All tool names follow the consistent 'get_<resource>' pattern in snake_case, making it predictable for an agent to infer the purpose of each tool from the name alone.

Tool Count5/5

13 tools is well-scoped for an analytics server covering site stats, sessions, funnels, campaigns, errors, and real-time data. Each tool earns its place without redundancy or unnecessary complexity.

Completeness4/5

The set covers the major analytics domains (traffic, engagement, campaigns, errors, funnels, real-time). Minor gaps exist, such as missing tools for goal/conversion tracking beyond funnels, but core workflows are well supported.

Resources