Skip to main content
Glama
Sign In
garmin-mcp-local

garmin-mcp-local

by the-mace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_sleep

Retrieve nightly sleep stages and sleep score breakdown for any date range.

Instructions

Nightly sleep stages + sleep score breakdown for a date range (inclusive, 'YYYY-MM-DD').

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_sleep"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It describes the data returned but does not disclose behavioral traits such as authentication requirements, rate limits, or read-only nature. The 'get' prefix implies a safe read operation, but not explicitly stated.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It covers the key elements: resource, action, and parameter format efficiently.

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?

Given the existence of an output schema, the description does not need to explain return values. It provides essential information about the data and parameters. Minor gap: it does not specify the user context or scope of data, but this is acceptable for a simple 'get' tool.

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?

With 0% schema description coverage, the description adds value by explaining the date range format ('YYYY-MM-DD') and inclusiveness. However, it does not differentiate between start_date and end_date or describe their individual semantics beyond the general range context.

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?

The description clearly states the tool retrieves 'Nightly sleep stages + sleep score breakdown' for a date range, specifying the inclusive format and date string pattern. It distinguishes from sibling tools like 'get_activity_detail' or 'get_daily_health_metrics' by focusing solely on sleep data.

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 description mentions the date range scope and format, but does not provide explicit guidance on when to use this tool versus alternatives, or any prerequisites or exclusions. Usage is implied but not fully clarified.

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