Skip to main content
Glama

log_habit

Record a habit completion in Lilt for today or backfill a past date. Identify the habit by id or name, and optionally set the day's total count.

Instructions

Log a habit completion in Lilt — today by default, or a past date to backfill. Identify the habit by id or name. Omit count to add one completion; pass count to set that day's total exactly (0 clears it).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "log_habit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoHabit id or unique prefix (see list_habits).
dateNoDay to log. Default today.
nameNoHabit name — exact or unique partial match.
countNoSet the day's count to exactly this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real mutation semantics: the default date, the backfill path, and the crucial distinction that omitting count adds one while passing count overwrites, including that 0 clears the entry. It stops short of saying what is returned, how future dates are rejected, or whether an unknown habit errors.

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?

Two sentences with no filler. The default behavior is front-loaded, and the count semantics arrive last as the most surprising detail, which is the right ordering.

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?

For a 4-parameter write tool with zero required parameters and no output schema, it covers the important ambiguity: defaults, backfill, and overwrite semantics. The remaining hole is what happens when neither id nor name is provided and whether both may be passed at once.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds genuine value by explaining the add-vs-set behavior of count that the schema does not state. It also notes identifying the habit by id or name, though it never says whether the two are mutually exclusive or what happens when neither is supplied.

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 definition uses a specific verb and resource ("Log a habit completion") and immediately states the default scope (today) plus the backfill case. Because the resource is a habit, it separates cleanly from the task-oriented siblings such as complete_task and create_task without needing to name them.

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

Usage Guidelines4/5

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

It gives clear conditions for the two modes: omit the date to log today, supply a past date to backfill, omit count to increment, pass count to overwrite. It does not name an alternative tool or state when not to use this one, which is the only gap.

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