Skip to main content
Glama
umami-compass

umami-compass

by webcredo

Get website data range

get_website_date_range
Read-onlyIdempotent

Retrieve the earliest and latest available analytics timestamps for a website to determine what date range of Umami data exists.

Instructions

Get the earliest and latest analytics timestamps available for a website.

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": {
      "websiteId": "<websiteId>"
    },
    "name": "get_website_date_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteIdYesUmami UUID

Output Schema

NameRequiredDescriptionDefault
dataYesJSON analytics data returned by Umami Compass
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.2
    • addedOutput schema / properties / meta / properties / responseTruncated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / meta / properties / sectionsTruncated
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / meta / required
      Previous value: -[
      -  "dataStatus",
      -  "truncated"
      -]New value: +[
      +  "dataStatus",
      +  "truncated",
      +  "responseTruncated",
      +  "sectionsTruncated"
      +]
  2. First observedv0.4.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld behavior, so the safety profile needs no restating. The description adds the shape of the result (two boundary timestamps) but says nothing about an empty-analytics case or an unknown websiteId, and the output schema covers the return format.

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?

One sentence, front-loaded with the verb and scope, with no preamble or filler. Slight redundancy in 'available for a website' keeps it from being maximally tight, but it is efficient overall.

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?

This is a simple single-parameter read with annotations and an output schema, so the description needn't explain return values. What it provides is sufficient to call the tool correctly; only the empty-data edge case is unaddressed.

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?

With a single parameter and 100% schema description coverage ('Umami UUID' with a UUID pattern), the schema already handles semantics. The description adds no further meaning about websiteId, such as whether it accepts a slug or name, which is the baseline expectation when coverage is high.

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 names a specific verb ('Get') and a precise resource ('earliest and latest analytics timestamps available for a website'), which is enough to distinguish it from get_website_stats or get_pageviews. It stops short of explicitly contrasting with those siblings, so it lands at a clear 4 rather than a 5.

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 never states when to use this tool versus alternatives, but the use case is strongly implied: confirm which date range has data before querying analytics endpoints. There are no exclusions, prerequisites, or named alternatives, so the guidance is only implied.

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