Skip to main content
Glama

list_clients_with_declining_recovery

Read-only

Clients whose sleep or resting heart rate (from Apple Health / Health Connect) is trending the wrong way over the window. Use get_recovery_signals for one client's detail.

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

Input Schema

NameRequiredDescriptionDefault
daysNoWindow in days (default set by the server)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 safety is covered; the description adds genuine context by naming the upstream data sources (Apple Health / Health Connect), which implies clients lacking wearable data may be absent. It does not disclose the threshold that defines 'declining', the result ordering, or how ties/insufficient-data clients are handled.

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 selection criterion and followed by the disambiguation pointer, with no redundant restatement of the tool name or annotations.

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 read-only list tool with one optional parameter and no output schema, the definition covers what the tool returns conceptually but leaves the agent guessing on the decisive detail: what counts as a declining trend, and whether clients without wearable data are excluded. Usable for invocation, but a probe or follow-up call would be needed 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?

The single `days` parameter is fully described in the schema (100% coverage, min 3 / max 90), so the baseline is 3. The description's 'over the window' merely echoes the parameter rather than adding format or defaulting behavior beyond what the schema already states.

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 (clients) qualified by a concrete signal set (sleep or resting heart rate from Apple Health / Health Connect) and a direction (trending the wrong way) over a window, which is enough to distinguish it from the other list_* siblings. It stops short of 5 because 'trending the wrong way' is directional-but-unquantified, so the agent cannot tell what magnitude of decline qualifies.

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

Usage Guidelines4/5

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

It explicitly routes the agent: use get_recovery_signals for a single client's detail, establishing this tool as the aggregate sweep. It does not state exclusions (e.g. what to use when you want improving clients), but the alternative-naming is clear enough for correct selection.

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.