Skip to main content
Glama

recent_habit_activity

Read-only

Recent habit completions across all of the coach's clients (newest first).

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": "recent_habit_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 useful behavior beyond that — newest-first ordering and that results span all of the coach's clients — but says nothing about the time window covered, whether the feed is truncated independent of `limit`, or whether clients with no activity are omitted.

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?

One sentence, no filler, with scope and ordering front-loaded. It is efficient but borders on under-specified for a feed tool, leaving no room for the return-shape or time-window detail an agent would want.

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?

The tool is simple — one optional, schema-bounded parameter, no output schema, read-only annotations — so the bar is low and the description covers scope and sort order. Still missing is what constitutes a 'completion' entry and the temporal window of 'recent', which an agent needs to interpret results.

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%, but the single `limit` parameter is fully constrained by the schema (default 20, min 1, max 100) and is self-explanatory. The description contributes only the ordering semantics ('newest first'), which is relevant but does not explain how `limit` interacts with that ordering.

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 resource ('habit completions') plus a clear scope ('across all of the coach's clients') and an ordering ('newest first'), so an agent knows it is fetching a cross-client activity feed rather than per-client metrics. It does not name sibling tools such as get_habit_adherence_all_clients or log_client_habit, so the differentiation is inferential rather than explicit.

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 cross-client scope implies this is the tool for a broad recent-activity view rather than a single-client lookup, which nudges selection correctly. However, there is no explicit 'use this when...' statement, no mention of when a per-client or adherence-oriented sibling would be better, and no prerequisites noted.

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.