Skip to main content
Glama

Log a habit

log_habit

Record a habit occurrence, including its tiny version, and receive the current weekly streak. Track progress without shame when gaps occur.

Instructions

Record that a habit happened (the tiny version counts). Returns the weekly streak so you can celebrate in one warm line. Never shame a gap.

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": {
      "habitId": "<habitId>"
    },
    "name": "log_habit"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
habitIdYes
versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully says the tool returns the weekly streak, but says nothing about idempotency (does logging the same date twice double-count?), whether dates default to today, or what happens with a date outside the current week. "Never shame a gap" is tone guidance rather than behavioral disclosure.

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?

Two short sentences, front-loaded with the action and immediately followed by the return value. The closing line is stylistic but brief and does convey expected framing of gaps, so little is wasted.

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 mutation tool with no annotations and no output schema, the description is thin: it never addresses repeat logging for the same date or default date behavior, which are the main failure modes for habit logging. The streak return is disclosed, but the write semantics are not.

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

Parameters2/5

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

Schema description coverage is 0%, so all three parameters rely on the description. Only the version enum gets indirect treatment ("the tiny version counts" implies tiny is a valid, non-penalized choice); habitId and the date pattern/format receive no meaning at all.

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?

"Record that a habit happened" gives a specific verb and resource, and the streak return value clarifies the effect. It does not distinguish itself from the sibling save_habit, so an agent cannot tell the two apart from the text alone.

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?

The parenthetical "the tiny version counts" hints that partial completion is valid, but there is no statement of when to use this versus save_habit or add_win, and no exclusions or prerequisites. Usage must be inferred.

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