Skip to main content
Glama

billiger_search_prices

Search billiger.de products by name for the 'ab' price in EUR, offer count, rating, and reviews. Query examples: iphone, samsung fernseher; optional result limit.

Instructions

Search billiger.de products by name: best ("ab") price in EUR, number of offers, rating and review count. query: e.g. iphone, samsung fernseher, waschmaschine. limit: 1..20 (default 10).

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": {
      "query": "<query>"
    },
    "name": "billiger_search_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the essential result shape (lowest price in EUR, number of offers, rating, review count), which is useful behavioral context, but says nothing about result ordering, fuzzy vs. exact matching, or rate limits/pagination.

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?

Purpose and result content are front-loaded, followed by parameter notes; no sentence is wasted. The line-broken, abbreviated phrasing is slightly clipped but stays compact and readable.

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-parameter search tool with an output schema present, the definition covers purpose, query format, limit bounds, and result contents. The main remaining gap is routing guidance relative to sibling price tools, which is minor given the tool's simplicity.

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 description coverage is 0%, so the description must compensate, and it largely does: 'query' gets concrete examples ('iphone, samsung fernseher, waschmaschine') and 'limit' gets an explicit range and default ('1..20 (default 10)'), adding real meaning beyond the bare schema types.

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 names a specific verb and resource ('Search billiger.de products by name') and enumerates what the results contain (best 'ab' price in EUR, offer count, rating, review count). It is not differentiated from siblings like billiger_product_offers or billiger_best_deals, but the purpose is immediately clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no mention of the sibling tools that also surface product/price data. The German-language query examples hint at the intended search mode, but the agent must infer when to choose this over billiger_product_offers or billiger_best_deals.

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