Skip to main content
Glama
mcp-server

mcp-server

by yasabbasi

metrics_daily_totals

Read-only

Retrieves published metric totals by day, week, or month for a start/end date range, returning aligned dates and values plus provisional flags for reporting and validation.

Instructions

The published totals from start to end (ISO dates, both included) by grain: day, week (starting Monday) or month. It returns columns: dates holds the first day of each period that falls in the range, and values holds one list per metric, lined up with dates. metrics picks the metrics; leave it out for all of them. At week and month, counts and money are summed and aov, return_rate and conversion_rate are recomputed from the summed parts; a ratio is null when its denominator is 0. Ratios are fractions between 0 and 1, rounded to four places. The session metrics, named in approximate, are approximate above day, because a session that crosses midnight is counted on both days. A period is provisional when any of its days is on or after restated_from, so its numbers may still change. Call metrics_freshness for the dates the data covers and metrics_list for the metric names.

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": "metrics_daily_totals"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
grainNoday
startYes
metricsNo

Output Schema

NameRequiredDescriptionDefault
datesYes
grainYes
valuesYes
approximateYes
provisionalYes
restated_fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare it is a safe read, and the description adds substantial behavior beyond that: aggregation rules (sums vs recomputed ratios), null-on-zero-denominator, four-decimal fractional ratios, approximate session metrics above `day`, and `provisional` periods tied to `restated_from`. These are exactly the semantics an agent needs to interpret results honestly.

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?

Dense but front-loaded, leading with the returned range and grain before qualifying edge cases. A single unbroken paragraph of clauses around `aov`, `return_rate` and `conversion_rate` is heavier than necessary, but almost no sentence is disposable.

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?

Given four parameters, 0% schema coverage and a read-only aggregation role, the description covers parameter meaning, aggregation semantics and edge cases thoroughly. It also explains return columns even though an output schema exists, which is slightly redundant rather than harmful.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does: `start`/`end` are inclusive ISO dates, `grain` enumerates day/week-starting-Monday/month with its effect on aggregation, and `metrics` selects metrics or defaults to all. Every parameter is given meaning beyond its type and default.

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?

States a specific verb and resource: it returns published metric totals from `start` to `end` at a given `grain`, and it names the columns produced. An agent can immediately distinguish this from `metrics_breakdown` or `metrics_explain` without opening another schema.

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?

Gives explicit operating guidance — omit `metrics` to get all of them, call `metrics_freshness` for date coverage and `metrics_list` for metric names. It lacks an explicit exclusion such as when the aggregation level of `metrics_breakdown` is preferable, so it falls short of full when/when-not routing.

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