Skip to main content
Glama

billiger_product_offers

Compare shop offers for one product, including seller, variant, price, shipping, total cost, and delivery time from a billiger.de URL, slug, or numeric ID.

Instructions

Compare shop offers for one product: shop, seller, variant, price, shipping, total and delivery time. product: a billiger.de /baseproducts/ URL, a slug (114326-apple-iphone-17) or a numeric id (114326). limit: 1..20 (default 10). Only the first 20 offers are on the page; total_offers reports the page total.

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": {
      "product": "<product>"
    },
    "name": "billiger_product_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
productYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one important behavior: only the first 20 offers are on the page and total_offers reports the page total, which warns the agent about truncation. It says nothing about rate limits, auth, ordering of results, or what happens with an unknown product id.

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?

Dense and front-loaded: the core purpose leads, then parameter formats, then the pagination caveat. Some phrases are compressed into run-ons ("shop, seller, variant, price, shipping, total and delivery time"), but no sentence is wasted.

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 field definitions need not be repeated. The description covers both parameters' accepted formats plus the 20-offer page cap, which is the main correctness hazard for this tool. Only selection guidance against sibling tools remains missing.

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 largely does: `product` accepts a billiger.de /baseproducts/ URL, a slug (114326-apple-iphone-17), or a numeric id (114326), and `limit` is documented as 1..20 with default 10. That is substantially more meaning than the bare schema types convey, though it omits what an invalid product yields.

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 ("Compare shop offers for one product") and enumerates the compared fields: shop, seller, variant, price, shipping, total, delivery time. It is clear what the tool returns, but it never distinguishes itself from the sibling billiger_search_prices, so an agent must infer which one handles single-product offer comparison.

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?

The usage is implied rather than stated: it is the tool for getting offers on one known product. There is no explicit when-to-use/when-not guidance and no reference to the siblings (search_prices, best_deals), so selection between them is left to inference. Acceptable but with a clear gap.

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