Skip to main content
Glama

Save a habit

save_habit

Create or update a goal-linked tiny habit with anchor, rhythm, barrier fix, if-then plans, and environment change; adjust status to shrink, pause, graduate, or drop, with capacity warnings.

Instructions

Create or update a tiny habit for a goal: a recipe ("After I [anchor], I will [tiny]"), its rhythm, the COM-B barrier and fix, if-then plans for obstacles and one environment change. Also use it to shrink, pause, graduate or drop a habit (status). Warns when active habits exceed what capacity allows.

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": {
      "goalId": "<goalId>"
    },
    "name": "save_habit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoPass to update an existing habit
fixNo
fullNo
tinyNoWhat they will do, starting with a verb, small enough to take under two minutes, e.g. "do one hip stretch"
anchorNoThe existing routine it follows, e.g. "After I make my morning coffee"
goalIdYes
ifThenNo
rhythmNo
statusNo
barrierNo
behaviourNo
environmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add one genuine behavioral trait beyond parameters — it 'warns when active habits exceed what capacity allows' — which is useful, but it says nothing about what an update does to omitted fields, whether changes are reversible, permissions, or what the response contains.

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 sentences, front-loaded with the primary create/update purpose before the secondary status mode and the capacity warning. It is dense but every clause maps to a real capability; the nested quoting around the recipe makes it slightly harder to parse but nothing is wasted.

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 12-parameter mutation tool with no annotations and no output schema, the description covers most field intent and one runtime behavior, which is reasonable. It falls short on the required goalId parameter, the distinction between 'tiny' and 'behaviour'/'full', and update semantics, so an agent still faces ambiguity on a few fields.

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 description coverage is only 25%, so the description must compensate, and it largely does: it explains the recipe format tying anchor+tiny, defines barrier/fix as a COM-B pairing, scopes ifThen to obstacles, and assigns status the meanings shrink/pause/graduate/drop. Remaining gaps are goalId (the only required field), 'behaviour', and 'full', none of which are explained.

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 opens with a specific verb pair and resource ('Create or update a tiny habit for a goal') and enumerates the concrete constituents of a habit (recipe, rhythm, COM-B barrier/fix, if-then plans, environment). It is clearly a persistence tool rather than a logging tool, though it never names a sibling such as log_habit to draw the boundary explicitly.

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 states two clear usage modes: creating/editing the habit definition, and using the status field to 'shrink, pause, graduate or drop' a habit. That gives an agent actionable context for when to reach for this tool, but there is no explicit when-not-to-use or named alternative for closely related operations like recording a completion.

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