Skip to main content
Glama
umami-compass

umami-compass

by webcredo

Analyze release impact

analyze_release_impact
Read-onlyIdempotent

Compare equal pre- and post-release windows across traffic breakdowns and Core Web Vitals to measure release impact, with summary or full detail.

Instructions

Compare equal pre- and post-release windows across traffic breakdowns and Core Web Vitals. Returns a compact executive summary by default; request full detail for drill-down evidence. Recent releases use a partial post window and an equally shortened pre window.

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>",
      "releaseAt": "<releaseAt>"
    },
    "name": "analyze_release_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
filtersNo
timezoneNoUTC
releaseAtYesUnix milliseconds, ISO 8601 with timezone, or YYYY-MM-DD (UTC)
websiteIdYesUmami UUID
dimensionsNo
windowDaysNo
detailLevelNosummary
otherReleasesNo
trafficSegmentNoall
includePerformanceNo

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
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuine interpretive context beyond them: default output is a compact executive summary, and recent releases produce a truncated post window with a correspondingly shortened pre window — a caveat that materially affects how results should be read.

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?

Three tight sentences, front-loaded with the core comparison, then output shape, then the window caveat. No filler or restatement of the tool name.

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

Completeness3/5

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

An output schema exists, so return-value detail is not required, and the description covers the key window semantics. However, for an 11-parameter analysis tool it never explains what the breakdowns/dimensions contain or how filters constrain the comparison, leaving the definition thin relative to the tool's complexity.

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

Parameters2/5

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

Schema description coverage is only 18%, so the description must carry parameter meaning. It only clarifies detailLevel (summary vs full drill-down) and the implicit windowDays/releaseAt relationship; dimensions, filters, trafficSegment, includePerformance, limit, timezone, and otherReleases are never explained, leaving most of the 11 parameters opaque.

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?

States a specific operation (compare equal pre-/post-release windows) over concrete resources (traffic breakdowns and Core Web Vitals), which is distinct from siblings like compare_traffic_series or explain_traffic_change. It stops short of explicitly naming the sibling it replaces, but the purpose is unambiguous.

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?

Offers real guidance for switching modes ('request full detail for drill-down evidence'), implying summary is the default consumption path. It does not say when to reach for this tool instead of explain_traffic_change or analyze_performance_portfolio, so alternative selection is left to inference.

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