Skip to main content
Glama
Mi Fitness MCP CN

Mi Fitness MCP CN

by ai-dachui

sync_data

Synchronizes Mi Fitness health data into a local SQLite database for AI querying and analysis, supporting date-range, hourly, background, and full or incremental sync.

Instructions

Synchronize Mi Fitness data

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sync_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoEnd date (YYYY-MM-DD or ISO 8601)
end_timeNoWindow end timestamp (epoch seconds)
backgroundNo
data_typesNo
hours_backNoFetch only the last N hours for time-series metrics
start_dateNoStart date (YYYY-MM-DD or ISO 8601)
start_timeNoWindow start timestamp (epoch seconds)
force_full_syncNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and provides none of it: nothing about whether sync is incremental by default, whether it blocks, how long it may take, whether it can fail partway, or whether it mutates local storage. Parameters like force_full_sync and background imply meaningfully different behavior modes that are never explained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but this is under-specification rather than conciseness: four words for an eight-parameter operation with no annotations. Nothing is said that could not be guessed from the tool name.

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

Completeness1/5

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

For an 8-parameter, zero-required, no-annotation, no-output-schema sync operation, the definition supplies none of the information an agent needs to invoke it safely — no default window behavior, no explanation of background or force_full_sync, no mention of what a sync returns or how to verify it succeeded.

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

Parameters2/5

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

Schema coverage is 63%, so several parameters (background, data_types, force_full_sync) are undocumented in both schema and description. The description adds nothing at all about the four date/time-window parameters or how start_date/start_time and end_date/end_time interact, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Synchronize Mi Fitness data" gives a verb (synchronize) and a resource (Mi Fitness data), so the core action is identifiable. However, it does not distinguish this from siblings like get_sync_status or get_data_coverage, leaving ambiguous whether this triggers a fetch, repairs gaps, or merely reports state.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite or trigger condition, and no mention of the related status/coverage tools an agent would naturally consult first. The agent must infer entirely from the name that this performs an actual sync rather than a status check.

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