Skip to main content
Glama

get_device_solar_data

Read-only

Retrieve per-day solar charging stats for a compatible Garmin device, including activity time gained, average and peak solar utilization, and minutes with solar input.

Instructions

Get solar data for a specific device

    Returns a per-day summary of solar charging for devices with solar panels
    (e.g., Instinct Solar, Fenix Solar): activity time gained from solar, and
    the average/peak solar utilization and minutes with solar input across the
    day's per-minute readings. Only applicable to solar-capable devices.

    Args:
        device_id: Device ID (can be obtained from get_devices)
        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": {
      "device_id": "<device_id>",
      "date": "<date>"
    },
    "name": "get_device_solar_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
device_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, open-world access, so the description adds the useful extras: the device-capability precondition and a description of what the per-day aggregate contains and is derived from ('the day's per-minute readings'). It doesn't mention paging, empty-result behavior, or date-range limits, but for a read-only getter the behavioral picture is solid.

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?

Front-loaded with the one-line purpose, then the return summary, then the applicability caveat, then the args — a logical order. The docstring-style 'Args:' block is slightly mechanical but every line carries information; nothing is filler.

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?

With no output schema and 0% schema coverage, the description carries the burden and largely meets it by describing both inputs and the shape of the returned daily summary. Missing only edge-case behavior (unsupported device, invalid date) for a fully complete definition.

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 description coverage is 0%, so the description must compensate, and it does for both params: device_id is described as coming from get_devices, and date is pinned to YYYY-MM-DD format. It does not address the integer-or-string union accepted by device_id, which is a minor remaining ambiguity.

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?

States a specific verb and resource ('Get solar data for a specific device') and immediately scopes it: per-day summary of solar charging for solar-capable devices, with named fields (activity time gained, average/peak utilization, minutes with solar input). No sibling tool in the list returns solar-specific metrics, so the agent can distinguish it readily.

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

Usage Guidelines4/5

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

Clearly says when it applies — only solar-capable devices (Instinct Solar, Fenix Solar) — and points to get_devices as the source of device_id. It does not explicitly say what to do for non-solar devices or whether to fall back to a general activity/step tool, which keeps it short of a 5.

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