Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Skill: analytics

get_skill_analytics
Read-onlyIdempotent

How to READ get_analytics: what every behavioral metric means (sessions, click/bounce rate, scroll/reading behavior, per-section click/exit/time distribution) and how to spot the weak section. Load before interpreting analytics or planning an optimization.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds real behavioral context: the payload is explanatory content covering metric definitions and a method for spotting the weak section, which the agent could not infer from the name or annotations.

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 front-loaded sentence with a dense but useful parenthetical inventory of covered metrics. No filler, though the capitalized 'READ' and mixed phrasing add minor noise.

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?

No output schema, so the description must convey what comes back — and it does, enumerating the metric families and the weak-section diagnostic. A note on the format of the returned guidance would be nice but is not essential for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the schema baseline of 4 applies. The description correctly implies no input is required to load the skill.

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?

It states the resource (behavioral analytics metrics from get_analytics) and the deliverable (meaning of sessions, click/bounce rate, scroll behavior, per-section distribution). The framing 'How to READ get_analytics' is slightly ambiguous about whether the tool fetches or explains data, but 'Load before interpreting' clarifies it is instructional content.

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?

'Load before interpreting analytics or planning an optimization' gives a concrete trigger and ordering relative to the get_analytics sibling. It stops short of saying when this is unnecessary (e.g., if you only need raw numbers), but the sequencing guidance is clear.

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

All Pageree toolsInspect
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.

Resources