Mi Fitness Data Bridge

Overview Schema Source Related Servers Discussions Admin

query_stress

Read-onlyIdempotent

Read stored Mi Fitness stress samples over an inclusive date range, optionally filter by low, medium, or high level, and paginate timestamped scores.

Instructions

Read device stress samples over an inclusive YYYY-MM-DD range, optionally filtered by level (low/medium/high). Returns data.samples [{timestamp, stress_score, level}] and data.count, earliest first. stress_score is the upstream device score, not a clinical assessment. limit defaults to 5000; use offset for subsequent pages. Use query_sleep for sleep quality rather than inferring it from stress. Read-only local SQLite query; no cloud request or automatic sync. Requires a configured local account/cache. Returns JSON text with status, source=cache, generated_at and data; empty lists mean no cached matches, not zero measurements. Use get_data_coverage to inspect availability or sync_data to refresh with user consent. Returns data.pagination {limit, offset, has_more, next_offset}; next_offset is null at the end. Keep filters unchanged and avoid syncing between pages.

Input Schema

TableJSON Schema

Name	Required	Description
`level`	No	Optional exact stored stress level: low, medium or high; omit to include all levels.
`limit`	No	Maximum records per page (1-5000); count describes this page only.
`offset`	No	Zero-based position; pass pagination.next_offset unchanged with the same filters.
`end_date`	Yes	Inclusive last calendar date, YYYY-MM-DD; must be on or after start_date.
`start_date`	Yes	Inclusive first calendar date, YYYY-MM-DD; must be on or before end_date. Uses stored calendar dates, not caller timezone conversion.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.4Sep 30, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum earliest matching records to return (default 5000); use a small positive value to limit context. No offset/cursor is available."New value: +"Maximum records per page (1-5000); count describes this page only."

addedInput schema / properties / limit / maximum
```
Added value: +5000
```

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based position; pass pagination.next_offset unchanged with the same filters.",
+  "minimum": 0,
+  "type": "integer"
+}

Changed13 schema fields changedv0.3.2Sep 21, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / end_date / description

Added value: +"Inclusive last calendar date, YYYY-MM-DD; must be on or after start_date."

addedInput schema / properties / end_date / examples
```
Added value: +[
+  "2026-01-15"
+]
```
addedInput schema / properties / end_date / format
```
Added value: +"date"
```
addedInput schema / properties / end_date / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```

addedInput schema / properties / level / description

Added value: +"Optional exact stored stress level: low, medium or high; omit to include all levels."

addedInput schema / properties / limit / default
```
Added value: +5000
```

addedInput schema / properties / limit / description

Added value: +"Maximum earliest matching records to return (default 5000); use a small positive value to limit context. No offset/cursor is available."

addedInput schema / properties / limit / minimum
```
Added value: +1
```

addedInput schema / properties / start_date / description

Added value: +"Inclusive first calendar date, YYYY-MM-DD; must be on or before end_date. Uses stored calendar dates, not caller timezone conversion."

addedInput schema / properties / start_date / examples
```
Added value: +[
+  "2026-01-15"
+]
```
addedInput schema / properties / start_date / format
```
Added value: +"date"
```
addedInput schema / properties / start_date / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```

First observedv0.3.0Aug 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover the safety profile (read-only, idempotent, non-destructive); the description goes well beyond them by disclosing the local SQLite/cache execution model, no cloud request or auto-sync, the local-account prerequisite, the semantics of empty result sets, the status/source/generated_at envelope, and the 'keep filters unchanged between pages' constraint.

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?

Front-loaded with purpose, scope, then return shape, then constraints. Dense but every line carries information; a few items (limit default, offset usage) mildly duplicate the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description specifies the returned envelope (status, source=cache, generated_at, data.samples fields, data.count, data.pagination with has_more/next_offset) and the caveat about the upstream device score not being clinical. Nothing needed to call or interpret it correctly is missing.

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 coverage is 100%, so start_date/end_date/level/limit/offset are already documented with formats, defaults, and bounds. The description adds only marginal context (limit defaults to 5000, offset for subsequent pages) that mostly restates the schema, so the baseline of 3 applies.

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?

States a specific verb+resource ('Read device stress samples') with the exact scope (inclusive YYYY-MM-DD range, optional level filter) and the return shape. Names the sibling it is not (query_sleep) so an agent can distinguish it immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit routing: use query_sleep instead of inferring sleep from stress, use get_data_coverage to inspect availability, use sync_data to refresh with consent. Also gives a when-not condition ('empty lists mean no cached matches, not zero measurements') and a pagination discipline rule.

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

Deploy Server

query_stress

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools