Skip to main content
Glama

get_fitness_age

Retrieve your Garmin Fitness Age estimate calculated from your fitness level, activity data, and body metrics.

Instructions

Get Garmin Fitness Age estimate based on fitness level, activity, and body metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Defaults to today if not provided

Implementation Reference

  • Registration + handler for the 'get_fitness_age' MCP tool. Calls client.getFitnessAge(date) and returns the JSON response as text content.
    server.registerTool(
      'get_fitness_age',
      {
        description: 'Get Garmin Fitness Age estimate based on fitness level, activity, and body metrics',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getFitnessAge(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Client method getFitnessAge that resolves the date (defaults to today) and makes a request to the FITNESS_AGE_ENDPOINT.
    async getFitnessAge(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${FITNESS_AGE_ENDPOINT}/${resolvedDate}`);
    }
  • Schema definition for the input parameter 'date' (optional YYYY-MM-DD string, defaults to today). Used as inputSchema for get_fitness_age.
    export const dateParamSchema = z.object({
      date: dateString
        .optional()
        .describe('Date in YYYY-MM-DD format. Defaults to today if not provided'),
    });
  • The registerPerformanceTools function that receives the server and client, and registers all performance tools including get_fitness_age.
    export function registerPerformanceTools(server: McpServer, client: GarminClient): void {
  • API endpoint constant: FITNESS_AGE_ENDPOINT = '/fitnessage-service/fitnessage' used by the client method.
    export const FITNESS_AGE_ENDPOINT = '/fitnessage-service/fitnessage';
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states the tool returns an 'estimate' based on certain metrics, but does not clarify if it requires prior data sync, what the output structure is, or whether it is a read-only operation. This is insufficient.

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, efficient sentence that conveys the core purpose without extraneous words. It is well-structured and front-loaded.

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?

Despite having no output schema, the description does not describe the return value or its structure. For a tool that produces an estimate, the agent needs to know what the response looks like (e.g., a number, object, units). This is a significant gap.

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

Parameters3/5

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

The input schema has 100% description coverage for the single 'date' parameter, including format and default behavior. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 retrieves a Garmin Fitness Age estimate using a specific verb ('Get') and resource ('Fitness Age'). However, it does not differentiate from sibling tools that also retrieve health metrics, such as get_vo2max or get_endurance_score.

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, caveats, or exclusions, leaving the agent to infer usage from the tool name alone.

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