Skip to main content
Glama

get_days

Read-onlyIdempotent

Fetch daily health data for a date range, oldest first, optionally limited to groups such as sleep, heart, or rings to track trends over time in one call.

Instructions

The day files of a date range (at most 366 days), oldest first, optionally reduced to the groups you name, so you can follow sleep, resting heart rate or rings over time in one call.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLast day, `YYYY-MM-DD` (inclusive, at most 366 days after `from`).
fromYesFirst day, `YYYY-MM-DD`.
groupsNoGroups to keep, e.g. ["heart", "sleep"]. Default: every group a day has.

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 readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful behavior beyond that: result ordering (oldest first), the 366-day cap, and the default of returning every group, but says nothing about response shape or size limits.

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?

A single front-loaded sentence that packs scope, ordering, filtering, and purpose with no filler. Slightly dense but every clause carries 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?

With no output schema, the description should convey what comes back; 'day files' plus the sleep/heart-rate/rings examples give an adequate sense of the payload. Minor gap is the absence of any note on response size or structure for a 366-day range.

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 coverage is 100%, so all three parameters are already documented, including the groups default. The description only restates the group filtering and date cap in prose, adding no syntax or format detail beyond the schema; baseline 3 applies.

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?

States a specific resource (day files) with scope (date range, at most 366 days), ordering (oldest first), and optional filtering by groups. It is clearly distinguishable from a single-day fetch, though it never names the sibling get_day explicitly.

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 phrase 'so you can follow sleep, resting heart rate or rings over time in one call' implies the time-series use case and hints at bulk-vs-single usage, but there is no explicit when-to-use/when-not guidance or named alternative such as get_day.

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