Skip to main content
Glama

create_habit

Create a routine: the planner places it once on each given weekday somewhere inside the window, flexibly around meetings.

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": {
      "title": "<title>",
      "durationMinutes": "<durationMinutes>",
      "weekdays": "<weekdays>",
      "windowStart": "<windowStart>",
      "windowEnd": "<windowEnd>"
    },
    "name": "create_habit"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNohabit = recurring routine, focus = protected focus time
titleYes
activeNo
priorityNo1 = niedrig, 2 = normal, 3 = hoch, 4 = kritisch
weekdaysYesISO weekdays, 1 = Monday
windowEndYesLatest local end, HH:MM
flexMinutesNoHow far the routine may move before or after its window on the same day when that helps the plan, e.g. lunch slightly later to keep a task in one piece; 0 (default) keeps it inside. Only set it when the user asks
windowStartYesEarliest local start, HH:MM
durationMinutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive write operation. The description adds useful behavioral context by explaining that the planner places the routine once per weekday within the window and may flex around meetings. It does not cover failure modes or permission requirements, but it meaningfully supplements the annotations.

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?

The definition is a single front-loaded sentence with no redundant wording. The core scheduling constraint and flexibility behavior are stated efficiently.

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 nine-parameter creation tool, the description explains the central scheduling model but leaves gaps around fields like title, durationMinutes, active, and priority. It is adequate given the partial schema descriptions, but it does not fully describe the tool's behavior or defaults.

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

Parameters3/5

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

Schema coverage is 67%, so several parameters are already documented, including kind, priority, weekdays, windowStart, windowEnd, and flexMinutes. The description reinforces weekdays, window placement, and flexibility around meetings, but it does not compensate for undocumented parameters such as title, durationMinutes, and active.

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 uses a specific verb and resource ('Create a routine') and explains that it is recurring across given weekdays inside a time window. It distinguishes itself from a one-off task by emphasizing routine placement, though it does not explicitly name sibling alternatives.

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 'Create a routine' and the scheduling behavior, making it clear this is for recurring routines rather than tasks. However, there is no explicit when-to-use guidance, no exclusions, and no direct comparison to alternatives such as create_task or create focus time.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources