Skip to main content
Glama
the-mace

garmin-mcp-local

by the-mace

backfill_batch_now

Run a controlled batch backfill for selected health categories (e.g., activities, sleep) to fetch historical data beyond prior exports. Call repeatedly to walk the full history without a single large fetch.

Instructions

Run one controlled batch of API-driven backfill per category, walking further back into history than the bulk export (or a prior backfill run) reached. Call repeatedly to walk the full history without one giant fetch.

`categories`, if given, restricts the batch to that subset (e.g.
["hrv_daily"]) instead of every category -- one of: activities,
daily_health_metrics, sleep, hrv_daily, training_readiness,
training_status, race_predictions, body_composition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
batch_daysNo
categoriesNo
earliest_dateNo2000-01-01

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided; description mentions 'controlled batch' and 'walk further back' but does not disclose whether it is destructive, idempotent, or what side effects occur. Lacks details on concurrency, rate limits, or result handling beyond walking history.

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?

Two concise sentences plus list of categories. Purpose is front-loaded. No unnecessary words. Could be slightly more structured but efficient.

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 output schema exists, return values not needed. But the tool has 3 parameters, only one partially explained. The missing explanation for batch_days and earliest_date leaves some ambiguity. Sibling context is provided, but the description does not fully address how this tool fits into the overall workflow with other sync tools.

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

Parameters2/5

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

Schema coverage 0%; description explains categories well but batch_days and earliest_date are not described. The parameter names are self-explanatory, but the description adds no extra meaning for those two. Only partially compensates for lack of schema descriptions.

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?

Clear verb and resource: 'backfill batch' per category. Distinguishes from siblings by being a controlled incremental walk, not a full sync. Explicitly states this tool is for repeated calls to cover full history.

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?

Says to call repeatedly, and explains the categories parameter to restrict. But no explicit comparison to sibling tools like sync_now or bulk export, nor conditions for when not to use. Implied usage is clear but not exhaustive.

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/the-mace/garmin-mcp-local'

If you have feedback or need assistance with the MCP directory API, please join our Discord server