Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

See where people click and scroll

analytics_heatmap
Read-onlyIdempotent

A page's heatmap: the most clicked elements with their text, rage clicks (3 fast clicks in one spot) and dead clicks (nothing on the page changed), how far down people scroll and time on page. The link opens the business's own page with the heat drawn over it (clicks, rage, dead, scroll; desktop, tablet or phone); it works for 7 days. The site's script records clicks on its own, without cookies or anything that identifies a visitor. Free.

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": {
      "site": "<site>",
      "page": "<page>"
    },
    "name": "analytics_heatmap"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoWith period custom: the last day.
fromNoWith period custom: the first day, 2026-10-01.
pageYesThe path, like /pricing.
siteYesThe site's domain (e.g. halversoncycle.example) or its site_id.
limitNo
deviceNoall
periodNo30d

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 declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the result is a link that draws the heat over the business's own page, the data only covers 7 days, and tracking is cookieless so no visitor is identified. That is meaningful behavioral disclosure for a reporting tool.

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?

Three sentences, front-loaded with what the heatmap contains, followed by the delivery mechanism and retention. The privacy/'Free' sentence is partly promotional, but it does contribute relevant context about cookieless tracking; overall it is dense but not padded.

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?

There is no output schema, and the description compensates by enumerating the returned metrics (top clicked elements with text, rage clicks, dead clicks, scroll depth, time on page) and the delivery format (link with heat overlay). Given 7 parameters at 57% schema coverage, the missing piece is date/limit semantics rather than the return shape.

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 57%, so roughly half the parameters are documented in the schema. The description only glosses 'desktop, tablet or phone' (device) and 'how far down people scroll', and says nothing about from/to, limit or the period enum including 'custom'. It adds flavor but does not compensate for the undocumented parameters, so the baseline 3 fits.

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 states a specific verb+resource: a page-level heatmap with clicked elements, rage clicks, dead clicks, scroll depth and time on page. That is far more concrete than the title 'See where people click and scroll'. It does not, however, distinguish itself from analytics_breakdown or analytics_stats, which an agent must reason about by name alone.

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 is implied by the data it returns (per-page engagement/click analysis), but there is no explicit 'use this when' or a named alternative such as analytics_stats for aggregate traffic or analytics_breakdown for segmentation. The 7-day window is mentioned, which helps scope expectations, but the agent still has to infer which analytics tool to pick.

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

All Conecto 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