Skip to main content
Glama

request_reload

Trigger a reload of epoch data for a specified YYYY-MM-DD date to refresh Garmin Connect metrics before reading or processing them.

Instructions

Request reload of epoch data

    Args:
        date: Date in YYYY-MM-DD format
    

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>"
    },
    "name": "request_reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare that this is a non-read-only, non-idempotent, non-destructive, open-world operation. The description adds no behavioral context beyond the date format: it does not explain whether the reload is asynchronous, what 'request' means in practice, what gets invalidated, or what the caller should expect afterward.

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 description is short and front-loaded with the core action. The 'Args' block is a small amount of schema restatement, but it carries the useful date-format detail and does not bloat the definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

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

For a mutating, open-world request tool with no output schema, the description is under-specified. It leaves out the effect of a reload, any async behavior, and any indication of scope or permissions, which are important for safely invoking this operation.

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 description coverage is 0%, so the description must compensate. It does provide the required date format (YYYY-MM-DD), which is meaningful beyond the untyped schema, but it does not explain what the date represents (e.g., which epoch or dataset is being reloaded).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Request reload of epoch data'), which is more specific than the bare tool name. However, 'epoch data' is undefined and ambiguous, and there is no differentiation from any sibling or explanation of what a reload actually affects.

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?

There is no when-to-use guidance, no prerequisites, and no indication of when this tool should be preferred over any alternative. The only guidance is the parameter format.

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