Skip to main content
Glama

get_hill_score

Retrieve your hill score for a specific date or date range, with optional daily, weekly, or monthly aggregation.

Instructions

Get Hill Score. Single date: omit endDate. Date range: provide both with optional aggregation (daily/weekly/monthly)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateYesStart date in YYYY-MM-DD format. If endDate is omitted, treated as single day
endDateNoEnd date in YYYY-MM-DD format. Omit for single-day view
aggregationNoAggregation for range mode: daily, weekly, or monthly. Only used when endDate is provided

Implementation Reference

  • The getHillScore method in GarminClient makes the actual API request to the Garmin endpoint. If no endDate is provided, it fetches a single-day score via HILL_SCORE_ENDPOINT with a calendarDate param. Otherwise it fetches a date range with aggregation appended to /stats subpath.
    async getHillScore(startDate: string, endDate?: string, aggregation = 'daily'): Promise<unknown> {
      if (!endDate) {
        return this.request(`${HILL_SCORE_ENDPOINT}?calendarDate=${startDate}`);
      }
      return this.request(
        `${HILL_SCORE_ENDPOINT}/stats?startDate=${startDate}&endDate=${endDate}&aggregation=${aggregation}`,
      );
    }
  • The MCP tool registration for 'get_hill_score' in the registerPerformanceTools function. It defines the tool's description and inputSchema (reusing getScoreSchema), and the handler calls client.getHillScore(startDate, endDate, aggregation).
    server.registerTool(
      'get_hill_score',
      {
        description:
          'Get Hill Score. Single date: omit endDate. Date range: provide both with optional aggregation (daily/weekly/monthly)',
        inputSchema: getScoreSchema.shape,
      },
      async ({ startDate, endDate, aggregation }) => {
        const data = await client.getHillScore(startDate, endDate, aggregation);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • The GetScoreDto type and getScoreSchema Zod schema used as input validation for get_hill_score. It validates startDate (required), endDate (optional), and aggregation (optional enum: daily/weekly/monthly).
    export type GetScoreDto = {
      startDate: string;
      endDate?: string;
      aggregation?: string;
    };
    
    export const getScoreSchema = z.object({
      startDate: dateString
        .describe('Start date in YYYY-MM-DD format. If endDate is omitted, treated as single day'),
      endDate: dateString
        .optional()
        .describe('End date in YYYY-MM-DD format. Omit for single-day view'),
      aggregation: z
        .enum(['daily', 'weekly', 'monthly'])
        .optional()
        .describe('Aggregation for range mode: daily, weekly, or monthly. Only used when endDate is provided'),
    });
  • The endpoint constant HILL_SCORE_ENDPOINT pointing to '/metrics-service/metrics/hillscore', used by the GarminClient to make the API call.
    export const HILL_SCORE_ENDPOINT = '/metrics-service/metrics/hillscore';
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, rate limits, or side effects. For a data retrieval tool, this is a significant gap.

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?

Two sentences, no wasted words. Purpose is front-loaded, and instructions are directly actionable.

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 low complexity (3 params) and no output schema, the description fails to explain what the tool returns or what a Hill Score represents. This limits the agent's ability to use the tool appropriately.

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?

Schema already provides full parameter descriptions at 100% coverage. The description adds useful context on parameter combination rules (single date vs range), exceeding baseline expectations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Get Hill Score' but does not define what a Hill Score is. The additional date parameter instructions clarify the operation scope, but the core purpose remains vague for an agent unfamiliar with the domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description clearly explains when to use single date vs date range, and how to set aggregation. However, it does not provide exclusions or alternatives among sibling tools.

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