Skip to main content
Glama

dm-drogerie-markt

by de.dm.mcp

Show Products as Cards

renderProductTiles
Read-onlyIdempotent

Retrieve dm-drogeriemarkt products and render them as a visual card grid (product image, brand, name, link to the product page).

USE WHEN: the user wants to see products, an overview of several products, or a picture/link instead of a text description

INPUT: DANs (7 digits, preferred) and/or GTINs (8-14 digits) multiple products can be requested at once min 1 / max 50. Use search tool first if only product name is known.

OUTPUT: card grid rendered by the host. found=false for unresolved IDs.

NOT FOR: ingredients, nutrition facts, allergens, warnings - the cards do not show them, use getProductDetails for those. Not for prices, availability, stock, reviews, recommendations.

ERRORS: validation error if >50 or no identifiers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dansNoDANs (exactly 7 digits, preferred over GTIN)
gtinsNoGTINs (8-14 digits)

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds important behavioral context beyond annotations: output is a host-rendered card grid, unresolved IDs yield found=false, and validation errors occur for >50 or no identifiers. This is valuable and consistent with annotations.

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?

The description is organized into clear labeled sections (USE WHEN, INPUT, OUTPUT, NOT FOR, ERRORS), with each line carrying actionable information. It is longer than average, but every section contributes to correct tool selection and invocation, making it efficient for its purpose.

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?

Given the tool's moderate complexity and lack of output schema, the description covers all key aspects: input constraints, output format, failure semantics for unresolved IDs, validation limits, and alternative tools. An agent can decide when and how to call this tool without ambiguity.

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 input schema already documents parameters with digit constraints and preference, and coverage is 100%. The description adds extra semantics: minimum 1 / maximum 50 products, both DAN and GTIN can be used together, and validation error conditions. This enhances schema-only knowledge.

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?

The description clearly states the tool retrieves dm-drogeriemarkt products and renders them as a visual card grid with specified fields (image, brand, name, link). It differentiates itself from siblings by explicitly excluding ingredients, prices, and other details that belong to getProductDetails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit USE WHEN and NOT FOR guidance, including when to prefer searchProducts if only a product name is known. It names the alternative tool (getProductDetails) for excluded use cases, making selection unambiguous.

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

All dm-drogerie-markt toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: findNearbyStores for location-based store search, searchProducts for finding products by query, and getProductDetails for retrieving detailed info by ID. No overlap in their core functions, and the descriptions explicitly clarify when to use which.

Naming Consistency5/5

All tool names follow a consistent verb_noun camelCase pattern: findNearbyStores, getProductDetails, searchProducts. The naming style is uniform and predictable.

Tool Count5/5

With 3 tools, the server is well-scoped for its apparent purpose of store locator and product information. Each tool covers a distinct need without redundancy or bloat, fitting comfortably within the ideal 3-15 range.

Completeness4/5

The core workflows are covered: finding nearby stores, searching products, and getting detailed product data. Minor gaps exist, such as lacking a direct store-by-ID lookup, but these can be worked around using existing tools and do not cause dead ends.

Resources