alcometer.de — Promillerechner

German drink-driving limits

german_drink_driving_limits

Read-onlyIdempotent

The blood alcohol limits in German road traffic (0.0, 0.3, 0.5, 1.1, 1.6 permille): who they apply to and the legal consequences (fines, points, driving bans, criminal offence). Text in German.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description usefully adds that the content is static reference material and that the text is in German, but says nothing about format, completeness of coverage, or how the values are structured.

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?

A single front-loaded sentence that names the domain first and then the content facets. Efficient, though the parenthetical threshold list is dense and could be structured more legibly.

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?

With no parameters and no output schema, the description carries the burden of describing the return content, and it does so by enumerating thresholds, applicability, and consequences. Minor gap: it does not indicate whether coverage is exhaustive or how the response is organized.

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?

The tool takes zero parameters, so the schema has no semantics to document; baseline is 4. The description correctly implies a parameterless, direct-lookup tool.

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 precise resource (German road-traffic blood alcohol limits) and enumerates the exact thresholds covered (0.0/0.3/0.5/1.1/1.6 permille) plus the associated consequences. It is clearly distinguishable from estimate_blood_alcohol (a computation) and list_drinks (a lookup of drinks).

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?

The implied use case — retrieving the legal reference values — is evident from the description, but there is no explicit statement of when to use this versus estimate_blood_alcohol, nor any prerequisite or exclusion. Routing is left to inference.

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

All alcometer.de — Promillerechner 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?