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

bosch-flow-mcp

by partymola
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bosch_get_capacity

Retrieve Bosch eBike battery capacity-tester diagnostic results to compare remaining capacity with the original specification, optionally filtering by battery part number or serial number.

Instructions

Get battery capacity tester diagnostic results.

Shows battery health data from Bosch's official capacity tester tool, typically done at dealer service appointments. Includes remaining capacity percentage vs. original specification.

Capacity-tester data comes only from the EU Data Act API; with a standard Bosch eBike Flow sign-in this is empty and the result explains why.

Args: part_number: Optional battery part number to filter results. serial_number: Optional battery serial number to filter results.

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_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
part_numberNo
serial_numberNo

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_capacityOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.1/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 the data source (EU Data Act API), the typical origin of the data, and the important edge-case behavior that the call returns empty with an explanatory message for standard sign-ins. It stops short of stating whether the call is read-only or what the empty/result payload structure looks like, though "Get" implies read.

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-loads the purpose, then adds the source/behavioral caveat, then the args. The prose is efficient, though the docstring-style "Args:" block is somewhat mechanical and the middle paragraph 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 two-optional-parameter read tool with no output schema and no annotations, the description covers what the data is and the important empty-result scenario. Minor gaps remain around the exact return shape and whether omitting filters returns all batteries, but nothing essential for correct invocation is missing.

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

Parameters3/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 compensate. It identifies both parameters as optional filters for part number and serial number, matching the schema titles, but adds little beyond that — no format hints, no note on what happens if both or neither are supplied, and no indication whether a top-level default returns all batteries.

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?

States a specific verb and resource ("Get battery capacity tester diagnostic results") and immediately narrows the scope to health data from the Bosch capacity tester with remaining capacity vs. original spec. This distinguishes it clearly from siblings like bosch_get_soc and bosch_battery_trends, which cover different data.

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?

Explains the real-world context (dealer service appointments) and, crucially, warns that with a standard eBike Flow sign-in the result is empty and explains why — effectively a when-not-to-use signal. It does not, however, name an alternative tool for standard sign-in users, so routing is implied rather than explicit.

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