Skip to main content
Glama

get_sleep_summary

Read-only

Retrieve a compact sleep summary for a date, returning essential metrics instead of bulky time-series data for daily health checks and LLM use.

Instructions

Get sleep summary with only essential metrics (lightweight version)

    This endpoint returns a compact summary of sleep data (~350 bytes) instead of
    the full granular data (~50KB). Ideal for daily health checkups and LLM integrations
    where the full time-series data would overwhelm the context window.

    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": "get_sleep_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

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 declare this is a safe read-only operation. The description adds valuable behavioral context beyond annotations by stating the response is ~350 bytes instead of ~50KB and is a compact summary of essential metrics, which helps an agent anticipate the lightweight return payload even though the exact metrics are not listed.

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 front-loaded and efficient, with the core purpose and size contrast stated first. The 'Args' formatting is slightly awkward but does not add unnecessary length.

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?

For a simple one-parameter read-only summary tool, the definition covers purpose, relative payload size, intended use cases, and date format. It does not enumerate the essential metrics included, but given the simple shape and annotation coverage, it is nearly complete.

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 carry parameter meaning. It specifies that the single 'date' parameter should be in YYYY-MM-DD format, which is useful guidance beyond the bare schema type.

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 states a specific verb and resource ('Get sleep summary') and immediately distinguishes it from the full granular sleep data endpoint by describing it as a lightweight compact summary. An agent can tell this is the compact daily sleep summary rather than the detailed time-series tool.

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?

It gives clear usage context: ideal for daily health checkups and LLM integrations where full time-series data would overwhelm the context window. It implies the alternative is the full granular data endpoint but does not explicitly name it or state when not to use this tool.

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