Skip to main content
Glama

create_habit

Create a habit for a client (confirm-gated). daysOfWeek: 0=Sun..6=Sat (empty = every day). reminderTime: 'HH:mm'.

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": {
      "clientId": "<clientId>",
      "name": "<name>"
    },
    "name": "create_habit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
emojiNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
categoryNo
clientIdYes
frequencyNoDAILY
daysOfWeekNo
descriptionNo
targetCountNo
reminderTimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds the confirm-gating behavior (a preview is returned when confirm is false), which is the most decision-relevant behavior of the tool. It says nothing about what the preview contains, error behavior, or whether creating a habit also assigns it to groups.

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?

Three short, front-loaded clauses with zero filler: purpose first, then the two ambiguous parameter conventions. The telegraphic style ('empty = every day') is dense but readable and each fragment carries information.

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?

For a 10-parameter mutation with no output schema, the description covers purpose, confirm-gating, and the two parameters whose encoding is non-obvious. Gaps remain: it does not describe what the preview returns or how the tool relates to master habits and group assignment, but nothing an agent strictly needs in order to invoke it correctly is missing.

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 description coverage is only 10% (only 'confirm' is documented), so the description must compensate. It does decode the two least obvious parameters: daysOfWeek (0=Sun..6=Sat, empty = every day) and reminderTime ('HH:mm'), which adds real meaning beyond the schema's bare 0-6 range and pattern. The remaining parameters (frequency, category enums, targetCount, emoji, description) are self-explanatory but entirely undocumented in either place.

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 and resource ("Create a habit for a client") with the affected entity clear. It does not distinguish itself from the many nearby sibling create tools (create_master_habit, assign_habit_to_groups, assign_master_habit), so an agent must infer from the name alone which creation path applies.

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?

"confirm-gated" implies a two-step preview-then-commit flow, which is genuine when-to-use guidance. However, it gives no guidance on choosing this over create_master_habit or assign_master_habit, and states no prerequisites such as the client needing to already exist.

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.