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

bosch-flow-mcp

by partymola
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bosch_get_soc

Retrieve live Bosch eBike battery state-of-charge, charging status, remaining energy, and reachable range per assist mode using a bike ID.

Instructions

Get live state-of-charge from the Bosch ConnectModule.

Returns real-time battery percentage, charging status, remaining energy, and reachable range per assist mode (eco/tour/sport/turbo).

Requires a ConnectModule on the bike. Data is only available when the bike is powered on, charging, or recently active.

Note: This calls the Bosch mobile API live - no caching.

Args: bike_id: The bike UUID from bosch_get_bikes.

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": {
      "bike_id": "<bike_id>"
    },
    "name": "bosch_get_soc"
  }
}

Input Schema

NameRequiredDescriptionDefault
bike_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_socOutput",
-  "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 Bosch mobile API call with no caching, that hardware prerequisites exist, and that data availability depends on bike state. It omits failure modes, latency, and rate-limit behavior, which is the main remaining gap.

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 action and return payload, then prerequisites, then the caching caveat, then args. Every sentence carries information, though the per-assist-mode enumeration is slightly more verbose than strictly needed.

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?

With no output schema, the description correctly takes on the job of describing return values, and it covers hardware requirements and availability windows. Missing only operational details such as auth expectations and error behavior for a live network call.

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%, so the description must compensate, and it does: bike_id is documented as a UUID and its provenance is given ('from bosch_get_bikes'), telling the agent where to obtain a valid value. That is meaningful information absent from the bare string 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?

States a specific verb and resource ('Get live state-of-charge from the Bosch ConnectModule') and enumerates the returned fields, which makes the tool's output scope concrete. The word 'live'/'real-time' implicitly separates it from siblings like bosch_battery_trends, but no sibling is named explicitly.

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?

Gives real preconditions for use: a ConnectModule must be installed and the bike must be powered on, charging, or recently active. It stops short of routing the agent to alternatives (e.g., bosch_battery_trends for historical data, bosch_get_capacity for capacity), so the when-not guidance is incomplete.

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