Skip to main content
Glama

bosch_get_bike

Retrieve detailed profile data for a single Bosch eBike by UUID, including brand, model, frame number, and component details from the cached API response.

Instructions

Get detailed profile for a single Bosch eBike.

Returns full bike details including brand, model, frame number, and the cached raw API response which may include component info.

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

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

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the return payload (brand, model, frame number, cached raw API response that may include component info), which is useful, but omits permission/auth requirements, error behavior for invalid UUIDs, and whether the cached response can be stale.

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?

Two front-loaded sentences plus a compact Args block; the primary purpose and return shape come first. The hedge 'may include component info' slightly weakens the return-value statement but nothing is extraneous.

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

Completeness3/5

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

For a single-parameter read tool with no output schema, the description covers purpose, parameter origin, and return fields. It leaves out error handling and the freshness/staleness of the cached raw API response, which matters for correct agent use.

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 does add two meaningful facts: the parameter is a UUID and it originates from bosch_get_bikes, which gives an agent a way to obtain a valid value, but it says nothing about format validation or failure modes.

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?

The description states a specific verb and resource ('Get detailed profile for a single Bosch eBike') and the singular scope implicitly contrasts with the plural bosch_get_bikes sibling. It stops short of naming the list tool as the alternative, but an agent can still tell single-item retrieval apart from the sibling list tools.

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 is only implied: the bike_id arg note ('from bosch_get_bikes') establishes the prerequisite workflow of listing first, then fetching detail. There is no explicit when-to-use versus siblings such as bosch_get_components or bosch_get_bikes, and no statement about what happens with an unknown ID.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.