Skip to main content
Glama

assign_master_habit

Assign a Master Habit to one or more clients — creates a habit per client (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": {
      "masterHabitId": "<masterHabitId>",
      "clientIds": "<clientIds>"
    },
    "name": "assign_master_habit"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
clientIdsYes
masterHabitIdYes

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 a non-read-only, non-destructive, closed-world write, and the description adds real value on top: a fan-out semantic ("creates a habit per client") and a confirm gate that yields a preview rather than executing. It does not address duplicate assignment, partial-failure behavior across multiple clients, or required permissions, keeping this below 5.

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?

One sentence that front-loads the action and scope, then adds two high-value clauses (per-client fan-out, confirm gate) with no redundant restatement of the tool name.

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 bulk mutation with no output schema, key information is missing: what the preview contains, whether re-assigning an already-assigned client is idempotent, and how failures for individual clients are reported. What is present is accurate and useful, but the definition does not fully cover the tool's 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?

With only 33% schema description coverage, the description must compensate, and it partly does: it clarifies the masterHabitId→clientIds relationship and that confirm gates execution. However, it never states that clientIds is a list of client identifiers or what the preview returns, so the two undocumented required parameters remain only loosely specified.

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 gives a specific verb plus resource ("Assign a Master Habit") and states scope ("to one or more clients"), which separates it from create_master_habit (creates the template) and assign_habit_to_groups (group targets). It stops short of naming a sibling as the alternative, so 4 rather than 5.

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 "to one or more clients" and "confirm-gated", which hints at a preview-then-execute flow, but there is no explicit when-to-use / when-not guidance or pointer to assign_habit_to_groups for group-level rollout. An agent can infer the context but must decide the alternative itself.

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.