Skip to main content
Glama
umami-compass

umami-compass

by webcredo

Get a portfolio analytics overview

get_portfolio_overview
Read-onlyIdempotent

Summarize aggregate traffic across visible websites for a bounded date range, highlighting period changes, growth and decline leaders, stale tracking, failures, and suspicious jumps.

Instructions

Summarize bounded aggregate traffic across visible websites, including period changes, growth and decline leaders, stale tracking, failures, and suspicious jumps.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "get_portfolio_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesUnix milliseconds, ISO 8601 with timezone, or YYYY-MM-DD (UTC)
startYesUnix milliseconds, ISO 8601 with timezone, or YYYY-MM-DD (UTC)
websiteLimitNo
staleAfterHoursNo
anomalyMinimumPageviewsNo
anomalyThresholdPercentNo

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

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real context beyond that: results are aggregated over 'visible websites' only (an implicit permission/scope constraint), and the output includes derived judgments (growth/decline leaders, stale tracking, failures, suspicious jumps) rather than raw counts. With an output schema present, it need not spell out return shape, so the remaining behavioral gaps are minor.

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 that packs the scope and the report contents without filler. It is dense but readable; the only cost is that the list of report sections crowds out any room for operational guidance.

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?

Purpose and report content are adequately covered and an output schema handles return values, so the core is complete. However, for a tool with four behavior-tuning parameters and a sibling set full of overlapping analytics tools, the definition leaves both tuning and tool selection entirely undocumented.

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 33% and four of six parameters (websiteLimit, staleAfterHours, anomalyMinimumPageviews, anomalyThresholdPercent) have no schema descriptions at all. The definition never mentions any of them, even though 'stale tracking' and 'suspicious jumps' are directly controlled by those knobs — the agent gets no hint that staleness and anomaly sensitivity are tunable or what the defaults mean. At low coverage the description should compensate and it does not.

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 gives a specific verb+resource: 'Summarize bounded aggregate traffic across visible websites', and enumerates what the summary contains (period changes, growth/decline leaders, stale tracking, failures, suspicious jumps). An agent can tell it produces a multi-section portfolio report rather than a raw metric series. It does not explicitly name how it differs from the closest sibling analyze_performance_portfolio, keeping it short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no alternatives named. 'Bounded' hints that a date range is required but nothing tells the agent whether to prefer this over get_metrics, analyze_performance_portfolio, or tracking_health_check for the same question. Usage must be inferred entirely from the purpose sentence.

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