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

bosch-flow-mcp

by partymola
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bosch_get_activity_detail

Retrieve a downsampled per-point track for a single Bosch eBike ride—including GPS, distance, speed, elevation, cadence, and rider power—using its activity ID.

Instructions

Get the per-point track for one ride (GPS + speed/elevation/cadence/power).

Live read. Returns a downsampled track (~500 points per ride): per-point cumulative distance (m), speed (km/h), elevation (m), cadence, rider power (W), and GPS lat/lon. Get the activity_id from bosch_get_activities.

Args: activity_id: The ride UUID from bosch_get_activities.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "bosch_get_activity_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes

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_activity_detailOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.2.3
  3. Removedv0.2.2
  4. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does real work: it declares 'Live read' (no caching, real-time fetch) and that the track is downsampled to roughly 500 points per ride, which materially changes how an agent should interpret the data. It does not mention pagination, empty/non-GPS rides, or error behavior, so it is not fully transparent.

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 with the one-line purpose, then return shape, then an Args block — good structure with no filler. Minor waste from the parenthetical metric list being partially repeated in the return sentence.

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 takes on the return-value burden and discharges it: it enumerates fields and their units (m, km/h, W, lat/lon) and flags downsampling. For a one-parameter read tool, nothing an agent needs to call it or interpret the result is missing.

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

Parameters4/5

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

Schema coverage is 0% — the single activity_id property has no description at all — so the description must compensate, and it does by identifying the value as 'The ride UUID from bosch_get_activities', which conveys both format (UUID) and provenance. That is exactly the information the schema omits.

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?

Specific verb plus resource: 'Get the per-point track for one ride' with the metric families in parentheses. It also implicitly distinguishes itself from the sibling bosch_get_activities, which is where an agent would otherwise be tempted to look.

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

Usage Guidelines4/5

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

Explicit routing is given for the prerequisite: 'Get the activity_id from bosch_get_activities.' That tells an agent where the input comes from, but there is no explicit when-not guidance (e.g. that this returns only one ride or what to do instead for aggregate stats across rides, which bosch_battery_trends may cover).

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