zoll.agency

Warennummer suchen

warennummer_suchen

Read-onlyIdempotent

Sucht mit Wörtern oder einer Nummer (2 bis 11 Ziffern) in der Kombinierten Nomenklatur und zeigt höchstens 10 Codes mit dem amtlichen Wortlaut, nach Code sortiert, ohne Rangfolge. Die achtstellige Warennummer gilt für Ausfuhr und Einfuhr; die 9. und 10. Stelle (TARIC) für die Einfuhranmeldung zeigt das Werkzeug nicht. Die Auswahl trifft der Nutzer. Verbindlich ist nur eine verbindliche Zolltarifauskunft (vZTA).

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": {
      "suchtext": "<suchtext>"
    },
    "name": "warennummer_suchen"
  }
}

Input Schema

Name	Required	Description	Default
`suchtext`	Yes	Ware oder Nummer (z. B. Kugellager oder 8482 10 90)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses the result cap (10), ordering (by code), absence of ranking, the exact field shown (amtlicher Wortlaut), and the deliberate omission of TARIC digits 9-10. It also states the legal limitation that only a vZTA is binding, which is critical context an agent would otherwise lack. This is substantially more than the annotations carry.

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?

Four compact sentences, front-loaded with the action and result shape, then scope limits, then the legal caveat. Every sentence carries information, though the TARIC and vZTA sentences could be tightened slightly without loss.

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 single-parameter, annotation-covered read tool with no output schema, the description covers everything an agent needs: what is searched, what comes back, how many results, how they are ordered, and what is deliberately not returned. The legal caveat closes the remaining risk of over-trusting the result.

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 100%, so the baseline is 3, but the description adds a real constraint the schema does not express: a numeric query must be 2 to 11 digits. It also clarifies that the single parameter accepts either free words or a code, reinforcing the schema example. No further syntax or format detail is given beyond that.

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 names a specific verb and resource ('Sucht mit Wörtern oder einer Nummer ... in der Kombinierten Nomenklatur') and states the output shape (max 10 codes, official wording, sorted by code). It also bounds scope by excluding TARIC positions 9-10, which separates it from declaration-oriented siblings. It never names an actual sibling tool, so routing is inferred rather than explicit.

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 implied: use it to look up a commodity code when the user must choose, and only a vZTA is binding. There is no explicit 'use this when / use X instead' guidance relative to ratgeber_suchen or the declaration tools. The closing disclaimers hint at when the result is not sufficient but do not name the alternative.

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

All zoll.agency 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?