Tarifkatalog

Search mobile tariffs

search_tariffs

Read-onlyIdempotent

Searches current German SIM-only mobile tariffs, or data-only tariffs, and returns them ranked, cheapest average monthly cost over 24 months first. Use it to find or compare tariffs by data volume, network, contract term, 5G, speed or provider. Returns at most 30 tariffs and the total number that match. Covers Germany only, SIM-only tariffs without a phone.

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

Input Schema

Name	Required	Description
`kind`	No	phone: tariffs with calls and texts (default). data: data-only tariffs for tablets, laptops or routers.
`sort`	No	price: average monthly cost over 24 months (default). monthly_fee: lowest first monthly fee. data: most data first. speed: fastest first.
`limit`	No	Number of tariffs to return, default 10.
`only_5g`	No	Only tariffs with 5G.
`language`	No	Language of the text fields and of the linked pages. Default de.
`networks`	No	Any of these networks; empty for all. d-netz: resellers that promise Telekom or Vodafone without saying which.
`provider`	No	Only this provider, by its slug as in the provider list, e.g. winsim.
`commitment`	No	none: cancellable monthly (prepaid included). prepaid: prepaid only. contract: minimum term of 12 months or more.
`allnet_flat`	No	Only tariffs with unlimited calls and texts to all German networks; ignored for data tariffs.
`min_data_gb`	No	Minimum high-speed data per month in GB; unlimited tariffs always qualify.
`unlimited_data`	No	Only tariffs with unlimited data.
`min_download_mbit`	No	Minimum advertised download speed in Mbit/s.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description layers on substantive behavior: default ranking by cheapest 24-month average cost, a hard cap of 30 results, and that the total match count is returned. It also discloses market/scope limits (Germany only, SIM-only, no phone) that no annotation conveys.

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

Conciseness5/5

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

Three tightly packed sentences: what it does, when to use it, and what comes back, with the ranking rule and result cap front-loaded. No filler or repetition of the title.

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 12-parameter, fully documented, all-optional search with no output schema, the description supplies the missing output contract (cap of 30, total match count, ordering) and the domain boundaries. The only residual gap is that it doesn't say whether results beyond 30 can be reached, though no offset parameter exists.

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?

Schema description coverage is 100%, so every parameter including the enums is already documented in detail; that sets the baseline at 3. The description only loosely gestures at the filterable dimensions ('data volume, network, contract term, 5G, speed or provider') without adding format or interaction semantics 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 (searches) plus resource (German SIM-only mobile tariffs), with the scope exclusions spelled out: 'Covers Germany only, SIM-only tariffs without a phone.' An agent can immediately tell this is a filtered list search rather than a single-record lookup like its siblings get_tariff/list_providers.

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?

'Use it to find or compare tariffs by data volume, network, contract term, 5G, speed or provider' gives a clear positive use case tied to the filter dimensions. It does not explicitly route away to get_tariff for a single tariff or list_providers for slugs, so exclusions/alternatives are left implicit.

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

All Tarifkatalog tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?