Skip to main content
Glama
shkyyy18

Mi Fitness Data Bridge

by shkyyy18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_sync_status

Read-onlyIdempotent

Check the status of a Mi Fitness data sync job using its sync_id. Returns state, timestamps, and result counts from the local database.

Instructions

Read one MCP sync job by sync_id, including after a server restart. Returns sync_id, status, timestamps and available result counts. States are queued, running, ok, partial, error, cancelled or interrupted (previous process stopped). Read-only local lookup; no cloud request. History retains the latest 500 completed jobs per account; unknown/expired IDs return status=error. Use query_sync_history to discover IDs, cancel_sync to stop a live background job, or get_connection_status for cloud connectivity. Restarted lookups omit raw error text for privacy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sync_idYesExact sync_id returned by sync_data or query_sync_history; not a workout ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.4
    • changedInput schema / properties / sync_id / description
      Previous value: -"Opaque ID returned by sync_data with background=true in this running server process; not a workout ID."New value: +"Exact sync_id returned by sync_data or query_sync_history; not a workout ID."
  2. Changed3 schema fields changedv0.3.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / sync_id / description
      Added value: +"Opaque ID returned by sync_data with background=true in this running server process; not a workout ID."
    • addedInput schema / properties / sync_id / minLength
      Added value: +1
  3. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: clarifies this is a local lookup with no cloud request, documents the 500-job retention window per account, states that unknown/expired IDs return status=error rather than failing silently, and notes that restarted lookups omit raw error text for privacy. These are behavioral facts an agent could not infer from readOnlyHint/idempotentHint alone.

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-loads the core purpose and return shape before the state list and routing guidance, and every sentence carries information. It is dense with four packed sentences, but none are wasted or redundant.

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?

With no output schema, the description still enumerates the returned fields and the complete state vocabulary, plus edge-case behavior for expired IDs and restarted processes. An agent has everything needed to call it and interpret the response correctly.

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 schema already defines sync_id, its format source, and that it is not a workout ID — establishing the baseline of 3. The description reinforces the lookup semantics (works after a restart, unknown IDs yield status=error) but adds no new syntax or constraint beyond the schema.

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 precise verb and resource ('Read one MCP sync job by sync_id') and enumerates the returned fields and the full set of possible states. An agent can distinguish it from get_connection_status and query_sync_history without opening any 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?

Explicitly routes to alternatives with conditions: query_sync_history to discover IDs, cancel_sync to stop a live job, get_connection_status for cloud connectivity. Also names the inverse relationship (IDs come from sync_data or query_sync_history), so the when-to-use picture is complete.

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

Deploy Server

Other Tools