Skip to main content
Glama

create_master_habit

Create a reusable Master Habit in the coach's library (confirm-gated).

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive write operation. The description adds that the action is confirm-gated and therefore preview-capable when unconfirmed, but it does not explain permissions, side effects, or what exactly is created beyond the resource name.

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 description is a single front-loaded sentence with no filler. It states the action, resource, location, and gating behavior efficiently.

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?

For a 7-parameter mutation tool with low schema description coverage and no output schema, the description is too thin. It covers the basic purpose and confirm gate but leaves most parameter semantics and behavioral details unaddressed.

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

Parameters2/5

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

There are 7 parameters with only 14% schema description coverage, so the description should compensate for missing field semantics. It only hints at the confirm gate and adds no meaning for name, emoji, category, frequency, description, or targetCount.

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 states a specific verb and resource: create a reusable Master Habit in the coach's library. This distinguishes it implicitly from client-habit creation and assignment siblings, though it does not explicitly name or compare 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?

The description implies usage for building a reusable library template rather than assigning a habit directly to a client, and it notes that creation is confirm-gated. It does not provide explicit when-to-use versus when-not-to-use guidance or name alternative tools.

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.