Skip to main content
Glama

Monthly habit-strength check

monthly_check

Record four SRBAI ratings (1–5) to assess a habit's automaticity and track monthly progress. An average of 4 or higher means the habit can graduate.

Instructions

Record the 4 SRBAI ratings (1–5) for one habit: "I do it automatically", "without having to consciously remember", "without thinking", "before I realise I'm doing it". An average of 4 or more means it can graduate.

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>",
      "ratings": "<ratings>"
    },
    "name": "monthly_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
habitIdYes
ratingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully adds the domain rule that an average of 4+ triggers graduation, which no annotation or schema field could express, but it omits the write semantics an agent needs: whether re-submitting overwrites or duplicates the month's record, whether the habit must exist first, and 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?

Two sentences, front-loaded with the action and immediately followed by the item definitions and the outcome threshold. The quoted statements are load-bearing rather than filler, and nothing is repeated from schema or title.

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 two-parameter tool with no output schema and no annotations, the domain explanation is strong but the operational side is thin: no return value, no duplicate-handling, no error conditions. Adequate to call the tool, not complete enough to call it safely twice.

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?

Schema coverage is 0% and the schema only constrains ratings to exactly four integers in 1-5 with no per-item meaning. The description supplies the missing semantics: the array is positional, one rating per listed SRBAI statement. That is the single most important fact for calling this tool correctly, though habitId is still only inferable from its name.

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 verb and resource are explicit ("Record the 4 SRBAI ratings ... for one habit"), and the four quoted statements define exactly what SRBAI means, which no sibling name conveys. It does not contrast itself with log_habit or quarterly_review, but the monthly/graduation framing makes the intent readable on its own.

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 rather than stated: the name 'monthly_check' plus "An average of 4 or more means it can graduate" tells the agent this is the periodic graduation gate, not a routine tally. There is no explicit when-to-use clause, no exclusion of log_habit, and no statement of what to do if a check was already recorded this month.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.