Skip to main content
Glama

Period statistics

zarok_get_period_stats
Read-onlyIdempotent

Returns statistics for a period of up to 185 days: totals, weekly trend, weekdays, time of day, categories, the most skipped and the most kept entries, the longest streak and the longest break. A day where the user restored the streak in the app continues the streak and is counted in streakSavedDays. Counts only. Read-only.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "zarok_get_period_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLast day of the period, YYYY-MM-DD; at most 185 days after from
fromYesFirst day of the period, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / from / description
      Added value: +"First day of the period, YYYY-MM-DD"
    • addedInput schema / properties / to / description
      Added value: +"Last day of the period, YYYY-MM-DD; at most 185 days after from"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds useful domain behavior beyond that: 'Counts only' and the streak-restoration rule clarifying that restored days continue streaks and appear in streakSavedDays.

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 three tight sentences with the core purpose front-loaded. The streak nuance and 'Counts only' constraint follow naturally, with no filler.

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?

Although there is no output schema, the description enumerates the returned statistics and clarifies the counting model and streakSavedDays semantics. Combined with complete parameter documentation and safety annotations, an agent has enough to call the tool correctly.

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 description coverage is 100%, so both 'from' and 'to' are already well documented in the schema, including the 185-day maximum. The description only restates the period limit and adds no parameter syntax or edge-case detail beyond the schema.

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 gives a specific verb and resource ('Returns statistics for a period') and enumerates the exact statistics returned, making its purpose immediately clear. The 185-day period scope distinguishes it from the sibling weekly summary tool.

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?

Usage is implied by 'statistics for a period of up to 185 days,' but the description never explicitly says when to choose this tool over alternatives like zarok_get_week_summary or zarok_get_habits. There are no exclusion conditions or named alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources