Skip to main content
Glama

add_body_composition

Record body composition metrics like weight, body fat, hydration, muscle and bone mass, BMI, and metabolic rates for a given date in Garmin Connect.

Instructions

Add body composition data

    Args:
        date: Date in YYYY-MM-DD format
        weight: Weight in kg
        percent_fat: Body fat percentage
        percent_hydration: Hydration percentage
        visceral_fat_mass: Visceral fat mass in kg (not grams)
        bone_mass: Bone mass in kg (not grams)
        muscle_mass: Muscle mass in kg (not grams)
        basal_met: Basal metabolic rate in kcal/day
        active_met: Active metabolic rate in kcal/day
        physique_rating: Physique rating
        metabolic_age: Metabolic age
        visceral_fat_rating: Visceral fat rating
        bmi: Body Mass Index
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "weight": "<weight>"
    },
    "name": "add_body_composition"
  }
}

Input Schema

NameRequiredDescriptionDefault
bmiNo
dateYes
weightYes
basal_metNo
bone_massNo
active_metNo
muscle_massNo
percent_fatNo
metabolic_ageNo
physique_ratingNo
percent_hydrationNo
visceral_fat_massNo
visceral_fat_ratingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare write semantics (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the safety profile is covered. The description adds the important unit constraint that several masses are in kg not grams, but says nothing about duplicate/overwrite behavior on the same date, which is the key risk implied by idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-line purpose is front-loaded and the Args list is dense with no filler; given that the schema has zero descriptions, each parameter line earns its place. The docstring-style indentation is slightly noisy but harmless.

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?

For a 13-parameter write tool with no output schema, the description covers purpose and every parameter well, but omits the two behavioral facts an agent most needs: whether adding a second entry for the same date duplicates or replaces data, and whether fields can be omitted/partially filled. Adequate, not complete.

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

Parameters5/5

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

Schema description coverage is 0% and there are 13 parameters, so the description carries the full burden — and it does, explaining each field including units (kg not grams), rate units (kcal/day), and the YYYY-MM-DD date format. This is precisely the value-add the schema lacks.

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 opening line states a specific verb and resource ('Add body composition data'), which is clearly distinct from the read counterpart get_body_composition. It does not explicitly name the sibling, so it lands just short of full differentiation.

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?

The description gives no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_body_composition or add_weigh_in. The agent must infer from the name alone that this is the write path for body composition measurements.

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