Skip to main content
Glama
GetSensr-io

Sensor Bio MCP Server

Official
by GetSensr-io

get_org_sleep_summary

Retrieves sleep summary data for all users in an organization, with options to specify a date, date range, or number of past days.

Instructions

Bulk: sleep summary across users in the org.

Date selection (mutually exclusive): date OR (start_date+end_date) OR days. Params:

  • date (YYYY-MM-DD, optional; default today)

  • start_date/end_date (YYYY-MM-DD, optional)

  • days (int>=1, optional)

  • max_users (int, default 50)

  • concurrency (int, default 5)

Returns: {range, users:[{user_id,days:[{date,data}],summary}], errors}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
daysNo
end_dateNo
max_usersNo
start_dateNo
concurrencyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/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 behavioral burden. It discloses mutually exclusive date modes, defaults, concurrency, and return structure. However, it states 'concurrency (int, default 5)' while the schema default is 3, making the behavioral guidance inaccurate and reducing trust.

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 and well-structured: a one-line purpose, a clear date-selection rule, a compact parameter list, and a return shape. Every sentence adds value and no content is redundant with the schema.

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 tool's complexity (bulk operation, 6 parameters, no annotations), the description covers date selection, limits, concurrency, and output. It does not explain pagination or behavior when max_users is exceeded, but the presence of an output schema and the parameter details make it sufficiently complete for agent invocation.

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%, and the description compensates by explaining all six parameters, including date formats, mutual exclusivity, and defaults. It loses a point because the stated concurrency default (5) contradicts the schema default (3), and 'date default today' is not reflected in the schema's null default.

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 'Bulk: sleep summary across users in the org,' clearly stating the resource (sleep summary), scope (all users in the org), and bulk nature. This distinguishes it from sibling tools like get_sleep (individual) and get_org_scores_summary (scores, not sleep).

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 'Bulk' prefix and 'across users in the org' provide clear context for org-level aggregation, implicitly contrasting with per-user tools. However, it does not explicitly name alternatives or give when-not-to-use guidance, so it stops short of a 5.

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