Skip to main content
Glama
Sign In
Mi Fitness MCP CN

Mi Fitness MCP CN

by binglua
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sync_data

Synchronize health data such as steps, heart rate, sleep, and workouts from Xiaomi Mi Fitness Chinese cloud to a local SQLite database for offline use.

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
data_typesNo
start_dateNo
end_dateNo
force_full_syncNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations provided. Description fails to disclose any behavioral traits: side effects, destructive nature, required connectivity, or whether it overwrites data. For a sync tool, this is a critical gap.

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?

Single sentence is concise but under-specified. The brevity is not efficient because it omits essential information; it is merely short.

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?

With 4 parameters, no output schema, and no annotations, the description is severely incomplete. Missing information about data types, date formats, sync mechanics, and expected outcomes makes the tool unsafe and unusable for an AI agent.

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

Parameters1/5

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

Schema description coverage is 0%. Description says nothing about what 'data_types', 'start_date', 'end_date', or 'force_full_sync' represent, format requirements, or default behavior. Adds zero value beyond schema.

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

Purpose2/5

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

Description states 'Synchronize Mi Fitness data', which is a tautology. It does not distinguish the tool from siblings (all get/query tools), nor does it specify what synchronization entails (push/pull/bidirectional). Minimal purpose clarity.

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

Usage Guidelines1/5

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

No guidance on when to use this tool vs alternatives. No context about prerequisites, ideal invocation timing, or scenarios where sync is appropriate. Completely absent.

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