Skip to main content
Glama

AICTIONBOT™ Werkbank

Claim a price reduction: has the market fallen since the last price agreement? Official Eurostat index, claim in percent and euros, ready message to the supplier

claim_price_reduction
Read-onlyIdempotent

The reverse of check_price_increase. Takes a category (call list_categories for the codes), the month of the last price agreement and optionally the annual volume. Compares the official Eurostat producer or service price index for Germany (and labour costs for services) between then and now. If the market has fallen by 1 percent or more it returns the claim in percent and euros per year, a ready message to the supplier, the three objections to expect and the next step. If the market has not fallen it says so plainly: no claim from the index. The index measures the market in Germany, not the supplier's own costs. Licence, or one free check every 30 days.

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": {
      "category": "<category>",
      "last_agreement": "<last_agreement>"
    },
    "name": "claim_price_reduction"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesCategory code or name from list_categories, for example C17 for paper and packaging.
languageNoLanguage of the answer. Default de.
supplierNoOptional: supplier name for the message.
last_agreementYesMonth of the last price agreement as YYYY-MM, from 2019-01.
annual_volume_eurNoOptional: annual purchasing volume with this supplier in euros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only and idempotency, and the description adds real context on top: the exact return payload (percent and euros per year, supplier message, three expected objections, next step), the important scope caveat that the index measures the German market not the supplier's own costs, and the licence/free-check-every-30-days limit.

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 but front-loaded: purpose first, then inputs, then outcome branches, then caveats and licencing. Opening with 'The reverse of check_price_increase' is slightly indirect relative to a direct statement of purpose, but every sentence carries information.

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?

For a read-only calculation tool with no output schema, the description fully covers inputs, both outcome branches, the contents of the response, the interpretive limitation of the index, and the usage limit. Nothing an agent needs to call or interpret it correctly is missing.

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?

With 100% schema description coverage the schema already documents every parameter, so the baseline is 3. The description adds only mild meaning — that category codes come from list_categories and that annual volume is used to derive the yearly euro claim — but no format or constraint detail 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?

States a specific verb and resource (claim a price reduction based on a Eurostat index between the last agreement and now) and immediately anchors it against the sibling check_price_increase by calling itself its reverse. An agent can tell what it produces without opening the schema.

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?

Explains the trigger condition (market has fallen since the last price agreement), routes the agent to list_categories for codes, and covers the negative outcome case where no claim is generated. It does not spell out an explicit when-not-to-use beyond that, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources