Skip to main content
Glama

Weekly review

weekly_review

Log a brief weekly check-in with energy, notes, and an optional good moment to review this week's habits and surface low-energy flags for timely reflection.

Instructions

5-minute weekly check-in: energy 1–10, a line on what helped or got in the way, and optionally one good thing this week and why it happened. Returns habits logged this week and a low-energy flag.

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": {
      "energy": "<energy>"
    },
    "name": "weekly_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
energyYes
goodThingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return payload ('habits logged this week and a low-energy flag'), which is genuinely useful, but it never states that calling it writes/records a review, whether a repeat call for the same week overwrites prior data, or what permissions are needed.

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?

A single dense sentence that front-loads the core action, enumerates the inputs in schema order, and ends with the return values. No filler or repetition.

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?

For a 3-parameter tool with no annotations and no output schema, the description covers inputs and return values adequately. What remains missing is the write/overwrite semantics and whether a prior week's review is replaced — material for a check-in tool that presumably persists data.

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 0% schema description coverage, the description must compensate and largely does: energy is bounded 1–10, 'note' is explained as 'a line on what helped or got in the way', and 'goodThing' is explained as 'one good thing this week and why it happened' plus marked optional. It adds real semantic meaning beyond the bare JSON types.

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 names a specific verb+resource: a '5-minute weekly check-in' that captures energy, a note, and an optional good thing. The weekly cadence implicitly distinguishes it from quarterly_review and monthly_check, though it never names those siblings explicitly.

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 'weekly check-in' and '5-minute', suggesting a recurring personal ritual, but there is no explicit when-to-use, when-not-to-use, or routing to an alternative such as monthly_check or save_reflection.

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