Skip to main content
Glama
Sign In
bosch-flow-mcp

bosch-flow-mcp

by partymola
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bosch_get_activities

Retrieve e-bike rides with per-ride distance, elevation, speed, power, cadence, assist-mode split, and CO2 metrics, filtered by date range, bike, or result limit.

Instructions

List e-bike rides with per-ride summary metrics.

Live read from the Bosch rider-activity API (no cache). Each ride includes distance, elevation gain/loss, avg/max speed, cadence, measured rider power, calories, rider-vs-motor energy share, assist-mode distance split (metres per mode), CO2 (emissions / car-equivalent / saved), and ABS/brake events. Heart rate is not recorded by the bike (it has no HR sensor) - pair with a wrist device for HR.

Args: start_date: Window start (YYYY-MM-DD, YYYY-MM, or "30d"). Default 30 days before the end or today, whichever is earlier. end_date: Window end. Default today. bike_id: Optional bike UUID filter. limit: Optional cap on rides returned (most recent first).

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": "bosch_get_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
bike_idNo
end_dateNo
start_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "bosch_get_activitiesOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.2.3
  3. Removedv0.2.2
  4. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that this is a live, uncached API read, enumerates the returned metric groups (energy share, assist-mode split, CO2, ABS/brake events), and flags the HR data limitation. Remaining gaps are ordering guarantees and pagination beyond 'most recent first,' but the disclosure level is well above baseline.

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-loaded summary sentence, then behavioral notes, then an Args block that mirrors the schema order. The metric enumeration is long but each item is a distinct returned field, so it earns its space; a couple of hyphenated clauses could be tightened.

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

Completeness4/5

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

For a four-parameter, unannotated, no-output-schema list tool, the description covers returned fields, defaults, data-source freshness, and a known data-absence caveat. Only edge details (timezone handling, behavior when bike_id is unknown, response envelope) are absent.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must do all the work, and it does: it gives start_date's accepted formats (YYYY-MM-DD, YYYY-MM, '30d') and its computed default, end_date's default, bike_id's UUID type, and limit's cap-with-most-recent-first semantics. Every one of the four parameters gains meaning unavailable in the schema.

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

Purpose4/5

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

Opens with a specific verb+resource ('List e-bike rides') and scopes it to 'per-ride summary metrics,' which implicitly separates it from bosch_get_activity_detail. It stops short of naming that sibling explicitly, so the differentiation requires a small inference.

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

Usage Guidelines3/5

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

Usage context is implied through the 'summary metrics' framing and the documented date-window defaults, but there is no explicit when-to-use-this-versus-that guidance and bosch_get_activity_detail is never mentioned. An agent must infer that this is the bulk/summary endpoint and the other is the per-ride drill-down.

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