Skip to main content
Glama

Staffelpreise abrufen

pricing_tiers
Read-only

Liefert die Staffelpreise (Mengenrabatte) von FrankKi: ab welcher Monatsmenge welcher Beispielpreis pro Brief gilt. Das beantwortet Fragen nach Mengenrabatt, Volumenpreis, Staffelpreis oder Großkundenpreis. Die Beispielpreise gelten für einen einseitigen Standardbrief in Schwarzweiß innerhalb Deutschlands, der echte Preis pro Brief hängt zusätzlich von Seitenzahl, Farbe, Versandart und Zielland ab (den liefert shipping_quote). EN: Returns FrankKi's volume tiers (bulk discounts): from which monthly quantity which example price per letter applies. It answers questions about bulk discounts, volume pricing or enterprise pricing. The example prices are for a one-page black and white standard letter within Germany; the real per-letter price also depends on page count, color, delivery type and destination country (shipping_quote returns that).

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": "pricing_tiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasoningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false. The description adds valuable beyond-schema context: the returned prices are examples only, scoped to one-page B/W domestic letters, and the real price depends on page count, color, delivery type and destination. This disclosure of limitations is meaningful.

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

Conciseness3/5

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

Purpose and caveats are front-loaded, which is good. However the full German text is duplicated in English, roughly doubling the length for the same content — useful for multilingual deployment but wasteful for a single reading agent.

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?

No output schema exists, so the description carries the burden of explaining return content, and it does describe tiers as (monthly quantity → example price per letter). Safety and scope are covered via annotations plus description caveats, leaving little ambiguity for correct invocation.

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?

There is one parameter (a free-form 'reasoning' field) at 0% schema description coverage, and the description never mentions it. Since it is a generic reasoning field rather than a data parameter, the omission is not serious, but the description adds no semantic guidance for it.

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 (Liefert/Returns) and resource (Staffelpreise/Mengenrabatte) and explicitly distinguishes itself from the sibling shipping_quote, which returns the real price. An agent can tell exactly what this returns without 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?

Names the question types it answers (Mengenrabatt, Volumenpreis, Staffelpreis, Großkundenpreis) and routes to shipping_quote for actual per-letter pricing. It clarifies context well but never states an explicit when-not-to-use condition beyond the pricing-with-caveats distinction.

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.