glasstopfen.de

Find set for vehicle

find_set_for_vehicle

Read-onlyIdempotent

Find the matching rear wiper hole plug set for a vehicle by make, model and optional model year. Returns UCP products.

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": {
      "make": "<make>",
      "model": "<model>"
    },
    "name": "find_set_for_vehicle"
  }
}

Input Schema

Name	Required	Description
`make`	Yes	Vehicle make, e.g. Volkswagen.
`meta`	No	UCP request metadata: {"ucp-agent": {"profile": "<platform profile URL>"}, "idempotency-key": "<uuid>"}.
`year`	No	Model year, e.g. 2019.
`model`	Yes	Vehicle model, e.g. Transporter T6.
`country`	No	Destination country, ISO 3166-1 alpha-2 (e.g. AT). Needed for final prices; without it prices are EUR estimates.
`language`	No	BCP 47 language for texts, e.g. de.

Output Schema

Name	Required	Description	Default
`ucp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that results are 'UCP products', without explaining what that means, whether an empty result is possible, or how pricing depends on country.

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?

Two short sentences, purpose front-loaded, no filler. The trailing 'Returns UCP products' is slightly vague but still earns its place as a scope signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the input schema is fully documented, so the core is covered. However, for a 6-parameter nested-schema lookup tool the description omits what happens on no-match and how country/language influence the result, leaving gaps.

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 the schema already documents make, model, year, country and language, including the note that country is needed for final prices. The description merely restates make/model/year and adds no syntax, format, or fitment caveats beyond the schema.

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?

States a specific verb and resource ('Find the matching rear wiper hole plug set') plus the scoping keys (make, model, optional year) and output domain (UCP products). It is clear on its own, though it never distinguishes itself from catalog/search siblings.

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 only implied: the vehicle-fitment framing suggests this is for finding a specific accessory set rather than browsing the catalog. There is no explicit when-to-use/when-not statement and no named alternative such as search_catalog or lookup_catalog.

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

All glasstopfen.de 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?