Fetch current user's Garmin Connect profile including display name, timezone, and activities to provide context for personalized health and activity insights.
Get the current user's Garmin Connect profile (display name, timezone, activities, etc.).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read operation through the verb 'Get,' but it does not mention authentication requirements, whether an active session is needed, or any other behavioral context like rate limits or data freshness.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with the core action and resource stated first, followed by a compact parenthetical of example fields. Every word earns its place with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no parameters and an output schema exists, so return values are already specified elsewhere. However, the description does not mention the likely prerequisite of being logged in, nor does it clarify the boundary with user_settings, leaving minor but real gaps for an agent deciding how to use it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema is empty and schema description coverage is 100%, so there are no parameters to document. The description adds useful context by framing the tool as operating on the current user's profile, making it clear that no arguments are required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and the resource ('current user's Garmin Connect profile'), with concrete examples like display name, timezone, and activities. It is clear and distinct from a generic stats or settings tool, though it does not explicitly differentiate itself from siblings such as garmin_user_settings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives like garmin_user_settings, garmin_stats, or garmin_daily_summary. The description implies it is for retrieving the current user's profile, but it offers no context, exclusions, or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.