Skip to main content
Glama

Dayze — Life Context

Sleep Summary

get_sleep_summary
Read-only

Sleep: day/week/month totals and averages. ($0.05; API key required)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sleep_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoSummary window: day, week or month, e.g. week.

Output Schema

NameRequiredDescriptionDefault
countYes
rangeNo
nightsNo
total_minutesNo
average_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / range / description
      Added value: +"Summary window: day, week or month, e.g. week."
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the remaining burden is light. The description adds two operationally important facts not in the structured fields: the $0.05 cost per call and the API key requirement. Return shape is covered by the output schema, so nothing critical is missing.

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?

Two terse fragments carry the purpose, the cost, and the auth requirement with zero filler. The resource label and the aggregate dimensions are front-loaded, and no sentence is wasted.

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 one optional enum param, an output schema, and full annotations, the description supplies enough to call the tool correctly, and adds cost/auth context on top. The one gap is routing guidance relative to get_sleep, which matters given overlapping sibling names.

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 100% and the single optional range parameter is fully described with an enum, so the schema already does the work. The description's 'day/week/month' phrasing merely echoes the enum values without adding format, default, or behavior detail. 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 the resource (sleep) and the specific content: day/week/month totals and averages. That distinguishes it conceptually from get_sleep/log_sleep, but the description never names a sibling or says how it differs from get_sleep, so differentiation is left to inference. The purpose itself is unambiguous.

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: nothing says to pick this over get_sleep for aggregate data versus raw records, nor any prerequisite beyond the API key note. Usage is only implied by the range enum. An agent must guess at the boundary between this and sibling sleep tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.