Skip to main content
Glama

create_habit

Define a new habit with name and type (Boolean or Real with measurable goal, step, unit). Optionally set color, reminders, recurrence, and encouragement.

Instructions

Create a new habit.

[Category: Habits]  [Auth: V2]
[Related: list_habits, update_habit, habit_checkin, build_recurrence_rule]
[Workflow: create_habit → habit_checkin daily → get_habit_records to review]

Args:
    name: Habit name (required).
    habit_type: "Boolean" (done/not done) or "Real" (measurable, needs goal).
    goal: Target value for Real habits (e.g., 2.0 for "2L water").
    step: Increment step for Real (e.g., 0.25 for quarter-liter).
    unit: Measurement unit for Real (e.g., "L", "pages", "min").
    color: Hex color, e.g. "#4DB6AC".
    icon: Icon resource name.
    section_id: Section ID (from list_habit_sections) for time-of-day grouping.
    repeat_rule: RRULE string (use build_recurrence_rule). Default = daily.
    reminders: Time strings, e.g. ["08:00", "20:00"].
    encouragement: Message shown on completion.
    target_days: Target days for the habit goal cycle.
    start_date: "yyyy-MM-dd".

Examples:
    Boolean: create_habit(name="Meditate", color="#7E57C2")
    Real:    create_habit(name="Read", habit_type="Real", goal=30, step=5, unit="pages")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
habit_typeNoBoolean
goalNo
stepNo
unitNo
colorNo
iconNo
section_idNo
repeat_ruleNo
remindersNo
encouragementNo
target_daysNo
start_dateNo
Behavior4/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 discloses the V2 auth requirement and describes parameter behavior (e.g., default repeat_rule, habit_type options). However, it does not explicitly state the return value or side effects (other than creation). This is adequate but could be improved by mentioning what the tool returns.

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?

The description is well-structured: a brief sentence, followed by metadata (category, auth), related tools, workflow, parameter list, and examples. It is front-loaded with purpose. While slightly verbose (e.g., the Args list repeats schema info), every section adds value, and the examples are helpful. Could be more concise without losing clarity.

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?

Given the tool has 13 parameters, no annotations, and no output schema, the description covers all parameters, provides examples, and suggests a workflow. It is missing explicit return value details and error handling, but for a creation tool, the description is sufficiently complete to guide an agent. The inclusion of related tools and workflow adds necessary context.

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

Parameters5/5

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

Schema description coverage is 0%, leaving the description to compensate. The description includes a detailed Args section that explains each parameter's purpose, defaults, and constraints in plain language (e.g., habit_type='Boolean' or 'Real', goal as target value, repeat_rule as RRULE). Examples further clarify usage. This adds significant meaning beyond the bare schema.

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 description clearly states 'Create a new habit.' and provides a verb+resource pair. It distinguishes from siblings by listing related tools (list_habits, update_habit, habit_checkin) and suggesting a workflow, showing how this tool fits into a sequence.

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?

The description provides explicit usage context: a workflow (create_habit → habit_checkin → get_habit_records) and examples for Boolean and Real types. It does not specify when not to use or exclusions, but the guidance is clear enough for an agent to decide when to invoke this tool versus its siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KpihX/tick-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server