Skip to main content
Glama

Week summary

zarok_get_week_summary
Read-onlyIdempotent

Returns counts of planned and completed entries for each of seven days from a start date. Use it for a quick look at one week; for longer periods use zarok_get_period_stats. 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>"
    },
    "name": "zarok_get_week_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesFirst day of the seven-day window, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / from / description
      Added value: +"First day of the seven-day window, YYYY-MM-DD"
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so "Read-only" is largely redundant. However, "Counts only" is genuinely additive: it tells the agent the response carries aggregates rather than entry details, which shapes downstream reasoning. The fixed seven-day window is also a behavioral constraint worth stating.

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 short sentences with the return shape first, the routing rule second, and the caveat last. Nothing is padded and no sentence repeats another.

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?

There is no output schema, but the description tells the agent it receives per-day planned/completed counts across a fixed seven-day window, which is enough to consume the result. Only exact field naming and empty-day handling are left implicit, a minor gap for a low-complexity read tool.

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

Parameters4/5

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

With one parameter at 100% schema coverage, the schema already documents the YYYY-MM-DD format and that it is the first day of the window. The description adds the semantic point that the window is exactly seven days, reinforcing what the parameter controls, though it adds no format 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?

States a concrete verb and resource (returns counts of planned and completed entries) plus the exact scope (seven days from a start date). It is clearly distinguishable from zarok_get_period_stats, which the description names explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

"Use it for a quick look at one week; for longer periods use zarok_get_period_stats" gives both the selecting condition and the named alternative. An agent needs no further inference to route between the two.

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