Skip to main content
Glama
GetSensr-io

Sensor Bio MCP Server

Official
by GetSensr-io

get_sleep

Retrieve sleep data for a user by date, date range, or number of past days. Returns summary and optional detailed time-series.

Instructions

Get sleep for a user.

Accepted date inputs (mutually exclusive):

  • date (YYYY-MM-DD, optional; default: today in SENSR_TZ or America/Chicago)

  • OR start_date/end_date (YYYY-MM-DD, inclusive)

  • OR days (int >=1): last N days ending today

Other params:

  • summary_only (bool, default true): if true, strips verbose time-series

Returns: {range, results:[{date,data}], summary}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
daysNo
user_idYes
end_dateNo
start_dateNo
summary_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: the default timezone (SENSR_TZ or America/Chicago), mutual exclusivity of date inputs, inclusive date ranges, and the effect of summary_only. It stops short of error handling or rate limits, but covers the core behavioral traits.

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 concise, front-loaded with the purpose, and structured with bullet-like lines for date inputs and other params. Every line adds value; no fluff or repetition.

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?

The description covers all six parameters, explains return structure, and captures the main behavioral nuances. It lacks edge-case details like max days or timezone definition, but given the output schema exists and the tool's moderate complexity, it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description is the only source of parameter meaning. It explains date, start_date/end_date, days, and summary_only with formats, defaults, and constraints. This fully compensates for the schema's lack of descriptions.

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 opens with 'Get sleep for a user', which is a specific verb+resource with clear scope. It distinguishes from the sibling 'get_org_sleep_summary' by explicitly targeting a single user, and from other get_* tools by focusing 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 Guidelines4/5

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

The description provides clear context on how to invoke the tool: three mutually exclusive date input modes, defaults, and the summary_only flag. It does not mention when to prefer this over alternatives like get_org_sleep_summary, but the usage patterns are well-specified enough for an agent to select it.

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