Bikefuchs — Bike Parts Price Comparison

Optimize Shopping Cart

optimize_cart

Read-onlyIdempotent

Find the cheapest way to buy multiple products together: computes the optimal split across shops — which items to order from which shop — accounting for each shop's shipping costs and free-shipping thresholds, and returns the lowest achievable total including shipping. Takes an array of EAN barcodes. For accurate results, call get_best_price for each EAN first, then call optimize_cart.

Input Schema

Name	Required	Description	Default
`eans`	Yes	Array of EAN barcodes (8–14 digit numbers as strings, e.g. '4524667749493'). NOT URLs.
`country`	No	Country for pricing and shipping (DE or AT, default DE)	DE

Output Schema

Name	Required	Description	Default
`disclosure`	No
`optimization`	Yes
`savings_info`	No
`stale_cache_warning`	No
`excluded_stale_offers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

addedOutput schema / properties / excluded_stale_offers

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "shops": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "shops"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 19, 2026
- addedOutput schema / properties / disclosure
```
Added value: +{
+  "type": "string"
+}
```
First observedJun 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context: it accounts for shipping costs and free-shipping thresholds and guarantees the lowest achievable total including shipping, which is more than the annotations convey.

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?

The description is front-loaded with the core behavior, then the input, then the prerequisite workflow. It stays efficient, though the first sentence's clauses are dense enough that the 'what it returns' point could be sharper.

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?

An output schema exists, so return values don't need explaining, and the description supplies the key workflow context that would otherwise be missing. It doesn't mention that only DE/AT are supported or the 20-EAN cap, but the schema covers both.

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 coverage is 100%, so both the eans array and the country enum are fully documented in the schema. The description only repeats that it takes an array of EAN barcodes and says nothing extra about country or the 20-item cap, so baseline 3 is appropriate.

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?

The description states a specific verb and resource — it computes the cheapest way to split a multi-item purchase across shops and returns the lowest total including shipping. It clearly distinguishes itself from siblings like get_best_price (single-item pricing) and get_shipping_breakdown (per-shop cost detail).

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?

It gives an explicit prerequisite: call get_best_price for each EAN first, then call optimize_cart. That sequencing guidance is concrete, though it doesn't say when *not* to use this tool or how it relates to get_shipping_breakdown for a detailed breakdown.

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

All Bikefuchs — Bike Parts Price Comparison tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.