garmin_list_accounts
Read-onlyIdempotent
List all Garmin logins linked to this install (id, email, label, created_at).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account | No |
Garmin Connect (treinos)
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is clear. The description adds that the tool lists 'all Garmin logins' but does not disclose additional behavioral traits (e.g., authentication requirements, caching). With annotations present, the description provides adequate but minimal extra context.
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?
The description is a single sentence that states the purpose and key fields without extra verbiage. It is front-loaded with the action and is highly efficient, earning its place with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a simple list operation, and the description covers the resource and output fields explicitly. There is no output schema, but the fields are enumerated. Minor gaps exist (e.g., no mention of pagination or limits), but overall the description is sufficient for a low-complexity tool.
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% for the single optional parameter 'account'. The description does not explain the parameter's purpose or how it affects the list. The description focuses on the output fields, leaving parameter semantics completely unaddressed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the tool lists all Garmin logins linked to the install, including the fields returned (id, email, label, created_at). The verb 'List' and resource 'Garmin logins' are specific, distinguishing it from sibling tools focused on authentication or workouts.
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 description implies usage for viewing linked accounts but lacks explicit when-to-use or when-not-to-use guidance. Sibling tool names (e.g., authenticate, connect, garmin_list_workouts) provide context, but the description does not directly address alternatives or conditions.
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.
TDQS
A3.6/5.0
Disambiguation5/5
Every tool has a clearly distinct purpose. The Garmin-specific tools each handle a unique operation on workouts or accounts, and the platform tools (authenticate, connect, marketplace, etc.) are separate and easily distinguishable.
Naming Consistency2/5
The naming is inconsistent: Garmin tools use a consistent 'garmin_verb_noun' pattern, but the platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) lack any prefix or pattern, creating a mismatch.
Tool Count4/5
With 16 tools, the count is slightly above the typical sweet spot but still justified. The domain of workout management requires several operations, and the platform utilities are essential for the server's operation within the MCP ecosystem.
Completeness4/5
The Garmin workout tools cover the full lifecycle: create, retrieve, update, delete, plus scheduling. Listing accounts and the platform utilities round out the surface. Minor gaps (e.g., no tool to fetch activities) are acceptable given the server's focus on 'treinos' (workouts).