Skip to main content
Glama

get_habit_compliance

Read-only

Habit compliance percentage (0-100) for a client over a date range (YYYY-MM-DD).

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>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "get_habit_compliance"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateYes
clientIdYes
startDateYes

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the return range (0-100) and the required date format, but says nothing about edge cases such as clients with no logged habits, whether the range endpoints are inclusive, or what value is returned when compliance is undefined.

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?

A single front-loaded sentence with no padding; the core measure and scope come first. It is a fragment lacking a verb, and its brevity comes partly at the cost of the omitted details noted elsewhere.

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?

With three required parameters and no output schema, the description gives the essential shape (percentage 0-100, date format) but omits what counts toward compliance, how missing data is handled, and range inclusivity. It is minimally viable rather than complete for a metrics endpoint.

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 0%, so the description must carry the load for three required parameters. It clarifies that one parameter is a client, gives the YYYY-MM-DD date format, and states the output scale, which partially compensates. It does not explain clientId sourcing/format or whether endDate is inclusive, leaving real gaps.

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 names a specific measure and scope: a habit compliance percentage for a single client over a date range. It is a noun phrase rather than a verb+resource sentence, but an agent can still identify the operation. It does not explicitly contrast with the sibling get_habit_adherence_all_clients, though the 'for a client' phrasing implicitly distinguishes it.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative despite an obvious sibling (get_habit_adherence_all_clients) that covers all clients. The date-range condition is stated as scope, not as selection criteria. An agent must infer usage from the name alone.

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.