Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_userprofile_settings

Read-only

Fetch the profile settings record from Garmin Connect's userprofile-service. Use it to read account profile preferences, separate from user-settings.

Instructions

The account's profile settings record, from /userprofile-service/userprofile/settings. Distinct from getUserSettings() ("user-settings"): the two paths are one character apart. GETs /userprofile-service/userprofile/settings (SINGULAR "settings", distinct from getUserSettings's "user-settings"; the two paths are one character apart and easy to transpose) Three profile endpoints, three methods: getUserProfile() reads /userprofile-service/socialProfile (and backs displayName/fullName/userName), getUserSettings() reads /userprofile-service/userprofile/user-settings (and back…

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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=true, so the safety profile is covered. The description adds endpoint-path context that helps disambiguate the call, but says nothing about the returned settings shape, latency, or error behavior. With annotations doing the heavy lifting, this is a modest but real contribution.

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

Conciseness2/5

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

The description restates the same path/sibling distinction three times ('Distinct from getUserSettings…', 'the two paths are one character apart', 'SINGULAR settings… one character apart and easy to transpose') and then terminates mid-sentence. It is not front-loaded and wastes a large fraction of its length on repetition.

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?

There is no output schema, so the description would ideally hint at what the settings record contains, but it does not. For a zero-parameter read tool with readOnlyHint annotations the essentials are present, yet the truncated ending leaves the sibling comparison unfinished.

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

Parameters4/5

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

The tool takes zero parameters (empty schema, additionalProperties false), so there is nothing for the description to disambiguate. Per the zero-parameter baseline this sits at 4; the description adds no parameter detail because none exists to add.

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?

States a specific resource — the account's profile settings record — and explicitly distinguishes it from sibling tools getUserSettings and getUserProfile by path. The verb is implied via 'GETs', so the purpose is recoverable, though the repetition about paths being 'one character apart' muddies rather than sharpens the distinction.

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?

It enumerates three related endpoints and their backing fields, which gives implicit routing guidance, and names the alternatives (getUserProfile, getUserSettings). However, it never states a clean when-to-use-this rule, and the text is cut off mid-sentence ('and back…'), so the guidance is incomplete.

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