Skip to main content
Glama

update_habit

Change a routine; active false pauses it without deleting.

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": {
      "id": "<id>"
    },
    "name": "update_habit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindNohabit = recurring routine, focus = protected focus time
titleNo
activeNo
priorityNo1 = niedrig, 2 = normal, 3 = hoch, 4 = kritisch
weekdaysNoISO weekdays, 1 = Monday
windowEndNoLatest 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
windowStartNoEarliest local start, HH:MM
durationMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false; the description adds genuine value by clarifying that deactivation is a pause, not a deletion, which is not derivable from the annotations. However, for a 10-parameter mutation it never says whether the update is partial or full-replacement, which is the single most important behavioral fact an agent needs.

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 compact clauses with no filler, and the core purpose is front-loaded before the clarifying behavioral note. It is efficient, though its brevity leaves obvious semantic gaps rather than being genuinely complete.

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?

With 10 parameters, no output schema, and only two annotations, the description leaves too much unsaid: partial-vs-full update semantics, what happens to unspecified fields, and the meaning of the scheduling parameters all go unaddressed. The single pause clarification does not carry the weight required at this complexity.

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 60% and the schema itself carries rich parameter detail (flexMinutes guidance, enum meanings, HH:MM patterns). The description only adds meaning for 'active'; the remaining nine parameters, including kind, priority, weekdays, and the time window fields, get no treatment beyond the schema.

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?

States a specific verb+resource ('Change a routine'), which is enough to distinguish it from create_habit/delete_habit siblings. It does not name the resource as 'habit' explicitly, nor differentiate from update_task or update_settings, but the intent is unambiguous.

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 only usage guidance is implicit, embedded in the pause behavior of one parameter ('active false pauses it without deleting'). There is no statement of when to use this tool versus create_habit, update_task, or replan, and no prerequisites or exclusions.

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