Skip to main content
Glama

update_habit

Edit a client's habit (confirm-gated). Pass habitId plus only the fields to change. frequency: DAILY | WEEKLY | SPECIFIC_DAYS. tracker: CHECKBOX | STEPS | WATER | COUNTER. category is a HabitCategory. daysOfWeek is 0..6 (Sun..Sat). Set isActive: false to pause a habit without deleting it.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
emojiNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
habitIdYes
trackerNo
categoryNo
isActiveNo
frequencyNo
daysOfWeekNo
descriptionNo
targetCountNo
reminderTimeNoHH:mm

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The '(confirm-gated)' note and the pause-not-delete hint add behavioral context beyond the annotations, but the confirm/preview mechanic is already spelled out in the schema's confirm parameter, so the description mostly echoes it. Annotations already supply the safe-mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds no information about what a partial update does to untouched fields 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence is front-loaded and load-bearing: scope first, then invocation rule, then per-field value vocabularies, then the pause idiom. No filler or redundancy, and the parenthetical enum lists read cleanly.

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 with no output schema and low schema coverage, the description covers the tricky enumerated fields but is silent on five parameters (name, emoji, description, targetCount, reminderTime) and on return behavior. It is adequate to invoke the tool correctly for the documented fields but leaves real gaps for the rest.

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?

With schema coverage at only 17% and zero enums declared in the schema, the description carries real weight: it enumerates the allowed values for frequency (DAILY | WEEKLY | SPECIFIC_DAYS), tracker (CHECKBOX | STEPS | WATER | COUNTER), the 0..6 Sun..Sat convention for daysOfWeek, and names HabitCategory for category. It leaves name, emoji, description, targetCount and reminderTime unexplained, but the enum disclosures are a genuine addition over 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?

The description opens with a specific verb and resource ('Edit a client's habit') and scopes it to a client's habit, which implicitly separates it from the sibling update_master_habit. It is clear and immediately actionable, though it never names the master-habit sibling 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?

'Pass habitId plus only the fields to change' gives concrete invocation guidance (partial update, habitId mandatory), and 'Set isActive: false to pause a habit without deleting it' steers the agent away from the remove/destructive path. It stops short of an explicit when-not-to-use statement or a named alternative tool.

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.