Skip to main content
Glama
Sign In
Mi Fitness MCP CN

Mi Fitness MCP CN

by binglua
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

query_workouts

Retrieve workout records from Mi Fitness by specifying date range, activity types, and optional duration or distance minimums.

Instructions

Query workouts

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "query_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_dateYes
end_dateYes
activity_typesNo
min_durationNo
min_distance_kmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations exist, so the description must disclose behavior. It only uses the generic verb 'query', which adds no insight into date-range requirements, output format, pagination, or read-only semantics.

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?

The description is extremely short but under-specified. This is not effective conciseness; it omits all useful information while taking up almost no space.

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?

Given five parameters, no output schema, and a sibling tool likely covering workout dynamics, the description is completely inadequate for correct selection or invocation. It provides no context about required date range or optional filters.

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%, and the description offers no explanation of the five parameters. The agent gets only names and types for start_date, end_date, min_duration, activity_types, and min_distance_km, with no units or format details.

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?

The description 'Query workouts' is a tautology that restates the tool name. It provides no detail about scope, filtering, or what distinguishes this from sibling tools like 'workout_series'.

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?

No guidance is provided on when to use this tool versus alternatives such as workout_series or query_metric_series. There is no mention of required inputs or typical use cases.

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