Skip to main content
Glama

get_client_workout_streak

Read-only

A client's current and longest workout-day streak, plus which streak badges they have earned.

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

Input Schema

NameRequiredDescriptionDefault
clientIdYesClient's User _id (from list_clients)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 content (current streak, longest streak, badges), which is genuinely useful because there is no output schema, but it does not disclose how a streak day is computed (timezone, whether today counts, what an empty history returns).

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 short sentence that front-loads the primary outputs (current and longest streak) before the secondary detail (badges). Every clause carries information; there is no filler.

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 simple one-parameter read with no output schema, the description covers the main returned fields, which is the essential part. It still leaves open the definition of a streak and behavior for clients with no workout history, which an agent would need to interpret results correctly.

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 coverage is 100% and the single parameter clientId is documented in the schema with its source (list_clients). The description adds no further meaning about the identifier, so the baseline 3 applies.

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 resource (workout-day streak) and the exact facets returned: current streak, longest streak, and earned streak badges. It is clearly a read of streak data rather than the raw logs that siblings like get_client_workout_logs would supply, though it never uses an explicit verb such as 'get' and does not name a sibling to contrast against.

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 guidance at all: nothing says to call this for gamification/progress summaries rather than pulling workout logs, and no prerequisites or alternatives are mentioned. The agent must infer the use case purely from the noun phrase.

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.