Skip to main content
Glama

get_goals

Read-only

Retrieve active, future, or past Garmin Connect goals to view distance or time targets with progress and remaining amounts.

Instructions

Get Garmin Connect goals (active, future, or past).

    Reads goals the way Garmin Connect's Goals page does, so named
    distance/time targets (e.g. a monthly cycling mileage goal) are
    included with their progress and remaining amounts. Falls back to
    python-garminconnect's get_goals() if that request returns nothing.

    Args:
        goal_type: Type of goals to retrieve. Options: "active", "future", or "past"
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
goal_typeNoactive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, non-destructive, open-world), so the bar is lower; the description still adds real behavior: results mirror Garmin Connect's Goals page, include named distance/time targets with progress and remaining amounts, and fall back to python-garminconnect's get_goals() when the primary request returns nothing. That fallback disclosure is genuinely useful for interpreting empty or unexpected results.

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 tight paragraphs plus a one-line argument note; the purpose leads, the behavior/fallback follows, and the parameter is documented last. No filler or repeated information.

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 single optional parameter with no output schema, the description covers what is returned (targets, progress, remaining) and the fallback path, which is the main edge case. Only minor gaps remain, such as pagination or behavior on invalid goal_type.

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 coverage is 0% and the schema has no enum, so the description carries the burden; it supplies the three allowed values for goal_type, which the schema does not. It does not restate the 'active' default or discuss behavior for invalid values, keeping it short of a 5.

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?

Names a specific verb and resource (get Garmin Connect goals) and scopes it to active, future, or past goals. That scope is enough to tell it apart from activity/step/body-battery siblings, though the description does not explicitly contrast with any sibling.

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

Usage Guidelines3/5

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

The goal_type options ('active', 'future', or 'past') imply how to select a result set, and the Goals-page analogy gives a mental model. There is no explicit when-to-use/when-not guidance or named alternative, so usage is inferred rather than stated.

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

Deploy Server

Other Tools