Skip to main content
Glama

get_habit_adherence_all_clients

Read-only

Habit adherence % and best current streak for every client over the window — the cross-client view. Use get_habit_compliance for one client's day-by-day.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_habit_adherence_all_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered, and the description adds what the payload conceptually contains (adherence percentage plus best current streak) rather than raw logs. It stops short of stating the default window when days is omitted or any pagination/result-size behavior across an entire client roster.

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 compact sentences: the first front-loads what the tool returns and its scope, the second handles disambiguation. Nothing is redundant or padded.

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 simple read-only aggregate with annotations covering the safety profile and no output schema to explain, the definition covers purpose, return contents, and routing. The remaining gap is the omitted default value and behavior of the 'days' parameter.

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?

The sole parameter 'days' has 0% schema description coverage — only min 1 / max 90 are encoded — and the description's phrase 'over the window' implies a lookback period but never states what the window defaults to or what unit semantics apply beyond days. With one low-coverage parameter, the description needed to compensate and largely does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete metrics returned (adherence % and best current streak), the population (every client), and the scope of aggregation (cross-client view), which distinguishes it from the per-client sibling without requiring the schema to be opened.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent: use this for the cross-client aggregate, use get_habit_compliance for one client's day-by-day detail. That is a named alternative plus the condition that selects it, which is the top of the scale.

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.