Skip to main content
Glama

get_personal_records

Retrieve your personal records including longest run, fastest 5K, 10K, half marathon, full marathon, and longest ride from Garmin Connect.

Instructions

Get personal records: longest run, fastest 5K/10K/half/full marathon, longest ride

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration for 'get_personal_records' with handler that calls client.getPersonalRecords() and returns the result as JSON text.
    server.registerTool(
      'get_personal_records',
      {
        description: 'Get personal records: longest run, fastest 5K/10K/half/full marathon, longest ride',
      },
      async () => {
        const data = await client.getPersonalRecords();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Registration of 'get_personal_records' tool on the MCP server via server.registerTool().
    server.registerTool(
      'get_personal_records',
      {
        description: 'Get personal records: longest run, fastest 5K/10K/half/full marathon, longest ride',
      },
      async () => {
        const data = await client.getPersonalRecords();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Client method getPersonalRecords() that makes an HTTP request to the personal record endpoint.
    async getPersonalRecords(): Promise<unknown> {
      return this.request(`${PERSONAL_RECORD_ENDPOINT}/${this.displayName}`);
    }
  • API endpoint constant for personal records: /personalrecord-service/personalrecord/prs
    export const PERSONAL_RECORD_ENDPOINT = '/personalrecord-service/personalrecord/prs';
Behavior2/5

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

No annotations are provided, and the description offers minimal behavioral insight. It does not disclose read-only status, authentication needs, or any side effects, which is insufficient for a tool with no annotations.

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 concise sentence that efficiently conveys the tool's 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description is somewhat lacking. It lists record types but does not explain the output structure, pagination, or whether all records are returned at once. Adequate but has gaps.

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 input schema has no parameters (100% coverage by default), so the baseline is 4. The description adds value by listing the types of personal records included, which is adequate.

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 verb 'Get' and the resource 'personal records', listing specific types (longest run, fastest 5K/10K/half/full marathon, longest ride). This distinguishes it from sibling tools like get_activities or get_activity_details.

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. It does not mention any context, exclusions, or alternatives, leaving the agent to infer usage.

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