KrystalView Analytics

Get Scroll Depth

get_scroll_depth

Read-onlyIdempotent

Get cumulative scroll-depth reach buckets for a specific page path.

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": {
      "path": "<path>"
    },
    "name": "get_scroll_depth"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Lookback period in days.
`path`	Yes	Page path to analyze, for example /pricing.

Output Schema

Name	Required	Description	Default
`data`	Yes	Scroll-depth reach buckets and page-level scroll engagement evidence.
`meta`	Yes	Site and rate-limit metadata for the current MCP call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds context about the output being 'cumulative scroll-depth reach buckets,' which clarifies the nature of the data retrieved, slightly enhancing transparency beyond annotations.

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 description is a single concise sentence with no wasted words. It is front-loaded with the core purpose, and every word is essential.

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?

Given the output schema exists (though not shown), the description does not need to detail return values. It adequately defines the tool's scope, though it could benefit from briefly mentioning the bucketing logic or typical use case.

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 description coverage is 100%, so baseline is 3. The description reinforces the purpose of the 'path' parameter but does not add new meaning beyond the schema definitions for 'path' and 'days.'

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 'Get cumulative scroll-depth reach buckets for a specific page path.' It uses a specific verb ('Get') and resource ('cumulative scroll-depth reach buckets'), distinctly separating it from siblings focusing on anomalies, campaigns, or sessions.

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 usage for a specific page path but provides no guidance on when not to use or alternatives. Siblings cover different analytics areas, but no explicit exclusions or contextual cues are given.

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

All KrystalView Analytics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.