Mi Fitness Data Bridge

Overview Schema Source Related Servers Discussions Admin

query_spo2

Read-onlyIdempotent

Read stored blood oxygen saturation samples from the local Mi Fitness cache across a date range, returning timestamps and SpO2 percentages.

Instructions

Read stored blood oxygen saturation samples (spo2_pct, percent) over an inclusive YYYY-MM-DD range. Returns data.samples [{timestamp, spo2_pct}] and data.count, earliest first. limit defaults to 5000; use offset for subsequent pages. These are device measurements, not a diagnosis; missing records do not indicate normal oxygen levels. Use query_heart_rate for bpm rather than oxygen saturation. 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
`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"
+}

Changed12 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 / 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?

With annotations already covering read-only, idempotent, non-destructive, and non-open-world behavior, the description adds substantial context beyond them: local SQLite query, no cloud request or automatic sync, configured account/cache requirement, empty-list semantics, pagination behavior, and output shape. It clearly discloses important operational and interpretation caveats.

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 with the core purpose and then moves through behavior, output, pagination, and caveats in a clear order. It is information-dense and mostly earns its length, though several pagination and output details are repeated across multiple sentences.

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?

There is no output schema, so the description carries the burden of explaining return values and does so thoroughly: data.samples with timestamp and spo2_pct, data.count, status, source, generated_at, and pagination fields. It also covers prerequisites, empty-results meaning, and pagination continuity, leaving little an agent needs 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 description coverage is 100%, so the input schema already documents all four parameters, including limit, offset, start_date, and end_date. The description repeats the inclusive date range, limit default, and offset usage but adds little parameter-level meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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: read stored blood oxygen saturation samples (spo2_pct, percent) over an inclusive date range. It distinguishes this from query_heart_rate by explicitly saying to use that tool for bpm rather than oxygen saturation. An agent can identify the tool without opening the schema.

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?

It gives explicit routing guidance: use query_heart_rate for bpm, get_data_coverage to inspect availability, and sync_data to refresh with user consent. It also warns that missing records do not indicate normal oxygen levels and instructs keeping filters unchanged between pages.

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

Deploy Server

query_spo2

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools