Skip to main content
Glama

Bikefuchs — Bike Parts Price Comparison

by com.bikefuchs

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

TableJSON Schema
NameRequiredDescriptionDefault
eansYesArray of EAN barcodes (8–14 digit numbers as strings, e.g. '4524667749493'). NOT URLs.
countryNoCountry for pricing and shipping (DE or AT, default DE)DE

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
optimizationYes
savings_infoNo
stale_cache_warningNo

TDQS

A4.5/5.0
Behavior5/5

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

Annotations indicate read-only, idempotent, non-destructive. Description reinforces this by describing a computation that does not modify state, and adds behavioral context (dependency on prior pricing calls). No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences tightly packed with essential information: function, input, and prerequisite. No redundancy or unnecessary details.

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?

Combined with annotations and schema, the description provides all necessary context: what the tool does, when to call it, and what it needs. Output schema covers return values, making the description complete.

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 covers 100% of parameters with descriptions. The description adds minor clarification (e.g., 'NOT URLs') but does not significantly enhance understanding beyond the schema.

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 explicitly states the tool computes the optimal split across shops to minimize total cost, including shipping. It specifies input (EAN barcodes) and clearly distinguishes from sibling tools by prescribing a prior call to get_best_price.

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?

Provides clear guidance: call get_best_price for each EAN first. Suggests appropriate usage context (after pricing) but does not explicitly state when not to use or list alternatives.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation2/5

The tools 'find_alternatives_for_product' and 'get_best_price' have nearly identical descriptions, both retrieving price and availability for a product by EAN. This creates confusion and likely causes misselection. Other tools are distinct, but this overlap significantly reduces clarity.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., get_best_price, resolve_product, search_product). No mixing of conventions or irregular naming.

Tool Count5/5

With 7 tools, the set is well-scoped for a bike parts price comparison server. Each tool serves a clear purpose in the shopping workflow, and the count is neither excessive nor insufficient.

Completeness4/5

The tool surface covers the core workflow: searching, resolving URLs, looking up by EAN, obtaining shipping info, and optimizing cart splits. The only minor gap is the redundancy between two nearly identical tools, but no essential operations are missing.

Resources