Skip to main content
Glama
Sign In
Health4AI

Health4AI

by jefflitt1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_workouts

Retrieve recent workouts from HealthKit, including type, duration, distance, and calories. Customize by time range and limit.

Instructions

Recent workouts with type, duration, distance, and calories.

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_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It does not disclose behaviors like authentication needs, rate limits, or whether it only returns a subset of data (e.g., pagination via limit). It only states what fields are returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but too brief for a tool with two optional parameters. It could add a second sentence explaining parameters without costing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description need not detail return values. However, with 0% parameter documentation and no usage guidance, it is incomplete for a tool that has configurable defaults and sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description contains no explanation of the two parameters (days and limit). The defaults are in the schema but not mentioned, leaving the agent uninformed about controlling the recency or number of results.

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 clearly states the tool returns recent workouts with specific fields (type, duration, distance, calories). It uses a specific verb and resource, but does not explicitly differentiate from sibling tools like compare_periods or get_daily_snapshot, though the focus on workouts is distinct.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context such as that it only returns recent data (default 30 days) or any limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools