Skip to main content
Glama

get_user_profile

Retrieve your Garmin Connect social profile including name, location, profile image, activity preferences, and fitness level.

Instructions

Get user social profile: name, location, profile image, activity preferences, level

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the get_user_profile tool logic by calling client.getUserProfile() and returning the result as JSON.
    async () => {
      const data = await client.getUserProfile();
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
      };
    },
  • Registration of the get_user_profile tool via server.registerTool with description metadata.
    export function registerProfileTools(server: McpServer, client: GarminClient): void {
      server.registerTool(
        'get_user_profile',
        {
          description: 'Get user social profile: name, location, profile image, activity preferences, level',
        },
        async () => {
          const data = await client.getUserProfile();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
  • Client method that calls the Garmin API endpoint for the user's social profile.
    async getUserProfile(): Promise<unknown> {
      return this.request(USER_PROFILE_ENDPOINT);
    }
  • The Garmin API endpoint constant for the user profile service.
    export const USER_PROFILE_ENDPOINT = '/userprofile-service/socialProfile';
Behavior2/5

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

No annotations exist, and the description only states what data is retrieved. It does not disclose whether the tool is read-only (implied by 'get'), whether authentication is required, or any side effects. Minimal behavioral transparency.

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 efficiently lists the returned fields. No unnecessary words, and it is front-loaded with the core purpose.

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?

While the description lists what is returned, it does not specify the scope (e.g., current user's profile only) or whether any input is needed. Given no output schema and no parameters, the description is adequate but could be more complete by clarifying context.

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 has zero parameters, and schema coverage is 100% (vacuously). Baseline score of 4 is appropriate as the description adds no parameter information, but none is needed.

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 states the tool retrieves the user's social profile and lists specific fields (name, location, profile image, activity preferences, level). It is a specific verb+resource combination, distinct from siblings which focus on health metrics.

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, such as get_user_settings or other profile-related tools. No exclusions or context are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nicolasvegam/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server