Skip to main content
Glama

billiger_best_deals

Retrieve today's deals from billiger.de with product names, starting EUR prices, and offer counts; set a limit from 1 to 20.

Instructions

Today's deals from the billiger.de home page: product, best ("ab") price in EUR and number of offers. limit: 1..20 (default 10).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "billiger_best_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

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?

With no annotations, the description carries the full behavioral burden. It does disclose the data source (the billiger.de home page) and the freshness scope ('today's'), which tells the agent the result set is limited to homepage-featured deals rather than a full catalog. It says nothing about ordering, rate limits, or whether the list is stable within a day.

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 short sentences, front-loaded with the resource and source, then the return shape, then the parameter constraint. Slightly telegraphic phrasing ('best ("ab") price') but nothing 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?

For a one-parameter listing tool with an output schema available, the description covers source, freshness, returned fields, and the limit constraint. Residual gaps (ordering, result stability) are minor and partly covered by the output schema.

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% for the single `limit` parameter, but the description fully compensates by stating the valid range 1..20 and the default of 10 — the range is information the schema does not contain. With only one simple parameter, this is close to complete.

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 gives a concrete verb+resource: retrieves today's deals from the billiger.de home page, and enumerates what each item contains (product, best 'ab' price in EUR, offer count). That is specific enough to separate it from search/offers siblings, though it never names them explicitly.

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: 'today's deals from the billiger.de home page' signals a browse-promotions use case rather than a targeted lookup, so an agent can infer it should pick this over a search tool for current specials. There is no explicit when-to-use/when-not-to-use statement or named alternative.

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