Skip to main content
Glama

get_floors

Get floors climbed chart data for a specific date to track daily stair climbing activity.

Instructions

Get floors climbed chart data for a specific date

Input Schema

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

Implementation Reference

  • The tool handler for 'get_floors'. It calls client.getFloors(date) and returns the floors chart data as JSON text.
    server.registerTool(
      'get_floors',
      {
        description: 'Get floors climbed chart data for a specific date',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getFloors(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Input schema for 'get_floors' - expects an optional date string in YYYY-MM-DD format.
    export const dateParamSchema = z.object({
      date: dateString
        .optional()
        .describe('Date in YYYY-MM-DD format. Defaults to today if not provided'),
    });
  • The GarminClient.getFloors() method that makes the actual API request using the FLOORS_CHART_ENDPOINT.
    async getFloors(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${FLOORS_CHART_ENDPOINT}/${resolvedDate}`);
    }
  • The API endpoint constant used by getFloors() to fetch floors climbed chart data.
    export const FLOORS_CHART_ENDPOINT = '/wellness-service/wellness/floorsChartData/daily';
  • The registerHealthTools function where 'get_floors' is registered on the McpServer.
    export function registerHealthTools(server: McpServer, client: GarminClient): void {
Behavior2/5

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

No annotations provided; description fails to disclose read-only nature or any behavioral traits beyond the schema.

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?

Single sentence with no wasted words, efficient and front-loaded.

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?

For a simple one-parameter tool, description is adequate; no missing critical context.

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?

Schema covers parameter details at 100%, so baseline is 3; description adds 'chart data' but no extra meaning.

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?

Description clearly states verb 'Get' and resource 'floors climbed chart data' for a specific date, distinguishing it from siblings like get_steps or get_heart_rate.

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 on when to use this tool versus alternatives, no context about prerequisites or use cases.

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