Skip to main content
Glama
rankin-works

Vetroscope MCP

by rankin-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get focus heatmap (hour × weekday grid)

get_focus_heatmap

Reveals when you usually work by returning a 168-cell weekly grid of active seconds. Filter by app, project, or tag to see patterns that hourly or weekday averages miss.

Instructions

Returns a dense 168-cell grid (7 weekdays × 24 hours) of active foreground seconds. Reveals when you usually do specific kinds of work — patterns the marginal hour-of-day and weekday distributions can't show. Optional app / project / tag filters narrow the heatmap to a single activity (e.g. 'when do I usually code in Cursor?'); the tag is matched by name (case-insensitive) or id, and include_descendants rolls up a parent tag's whole subtree. Cells array is in (weekday, hour) order so cells[w*24 + h] indexes directly. 0=Sunday in weekday.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoRestrict to a single app (canonical name)
tagNoRestrict to entries carrying this tag (name, case-insensitive, or numeric id)
deviceNoRestrict to a single device. Pass 'current' (or 'this') for the local machine, a device UUID from get_device_breakdown, or a platform name like 'darwin', 'win32', 'browser-extension'. Omit or pass 'all' for no device filter.
periodNotoday | yesterday | week | month | year | a single date YYYY-MM-DD | an inclusive date range YYYY-MM-DD..YYYY-MM-DDmonth
projectNoRestrict to a single project (exact match)
include_descendantsNoRoll up the tag's whole subtree (the tag plus all of its nested child tags) instead of only its directly-assigned time. Use for a parent tag whose time lives in its children. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.10
    • addedInput schema / properties / include_descendants
      Added value: +{
+  "description": "Roll up the tag's whole subtree (the tag plus all of its nested child tags) instead of only its directly-assigned time. Use for a parent tag whose time lives in its children. Default false.",
+  "type": "boolean"
+}
    • changedInput schema / properties / tag / description
      Previous value: -"Restrict to entries carrying a tag with this exact name"New value: +"Restrict to entries carrying this tag (name, case-insensitive, or numeric id)"
  2. First observedv1.2.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses the exact cell ordering, weekday numbering (0=Sunday), tag matching semantics, include_descendants behavior, and the nature of the data (active foreground seconds). No contradictions or missing critical behaviors.

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 compact and front-loaded: the first sentence states the core output, the second explains value, and the third covers parameter behavior and indexing. Every sentence earns its place with no filler or repetition.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema and six optional parameters, the description provides a complete mental model: output shape, cell ordering, filter semantics, and descendants behavior. It also adds practical indexing guidance that compensates for the missing output schema.

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 the schema already documents all six parameters with descriptions. The description adds a few clarifying examples and reiterates tag matching/descendants, but these are largely redundant with the schema, so the baseline 3 is appropriate.

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 uses a specific verb ('Returns') and precisely names the resource ('dense 168-cell grid of active foreground seconds'), which clearly distinguishes it from sibling breakdown/stat tools. The added context about revealing interaction patterns further reinforces its unique purpose.

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?

The description explains when to use this tool ('Reveals when you usually do specific kinds of work') and contrasts it with marginal distributions, implying a comparison to aggregate breakdown tools. However, it does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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

Deploy Server

Other Tools