Skip to main content
Glama

Quarterly review

quarterly_review

Run a 30-minute review to re-rate life areas, keep or drop goals, and log an optional note; returns each area's change since the last baseline.

Instructions

30-minute reset: new life-area ratings, which goals stay, and an optional note (e.g. a gratitude letter written). Returns the change in each area since the last baseline.

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": {
      "areas": "<areas>"
    },
    "name": "quarterly_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
areasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that it returns per-area deltas against the last baseline, but it never says whether the new ratings overwrite the baseline, what happens to areas not supplied, or whether the operation is reversible — critical for a mutation tool.

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 dense sentence with the scope and return behavior front-loaded; '30-minute reset' sets useful framing rather than being pure filler. Nothing is repeated or redundant.

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

Completeness2/5

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

For a tool with a nested object parameter, no annotations, no output schema, and 0% schema coverage, the description leaves too much open: baseline prerequisite, overwrite semantics, and the unexplained goals-retention claim. The partial return-value hint helps but does not close the gap.

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 0%, so the description must compensate: it does establish that 'areas' is a life-area-to-rating map and that 'note' is optional free text with an example. However, it omits the 1-10 scale semantics and, worse, refers to 'which goals stay' even though no goals parameter exists, leaving the mapping ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the activity (a quarterly reset that captures new life-area ratings and an optional note) and even sketches the return value, but the operative verb is fuzzy ('reset') and it never distinguishes itself from weekly_review or monthly_check, which an agent must choose between. 'Which goals stay' muddies the purpose further, since no goals input exists.

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 guidance versus the obvious siblings (weekly_review, monthly_check) and no stated prerequisites, even though 'since the last baseline' implies save_baseline must have been run first. An agent has to infer the cadence distinction from the tool name alone.

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