Skip to main content
Glama

dm-drogerie-markt

by de.dm.mcp

Get in-store product availability

getStoreAvailability
Read-onlyIdempotent
        Check whether one or more dm-drogeriemarkt products are available in one or more
        specific stores right now.

        USE WHEN: you need to know if one or more products can currently be bought in one or
        more particular physical stores.

        INPUT: one to five storeIds and one to ten DANs (dm product numbers).

        OUTPUT: for each requested DAN, whether it was found and a status per requested
        storeId - VERFUEGBAR (available, includes current stockLevel), NICHT_VERFUEGBAR (not
        available in this store right now), NUR_ONLINE (this product is not carried in ANY
        dm store, not just this one), PRODUKT_UNBEKANNT (DAN not found), or STORE_UNBEKANNT
        (storeId does not exist in our system).

        IMPORTANT: NUR_ONLINE means the product itself is never sold in physical dm stores -
        it will be the same result for every store. Do not check other or nearby stores for
        that product; tell the customer it is online-only right away.

        IMPORTANT: storeIds MUST come from the findNearbyStores tool - call it first to
        resolve the storeId(s) for a location. Never invent, guess, or otherwise make up a
        storeId yourself; a made-up storeId will come back as STORE_UNBEKANNT instead of a
        real availability answer.

        IMPORTANT: if a customer asks about availability for several products, pass ALL of
        their DANs (up to 10) into this single call. Never assume, infer, or extrapolate the
        availability of a product you have not included in a call and gotten a result for -
        not even from a similar or already-checked product, and not even for "usually
        available" items. When reporting back, state the result for every single product
        individually (e.g. one line per product) - never collapse multiple products into one
        summary statement such as "all of them are available".

        TIP: if a product's result is NUR_ONLINE, or it is NICHT_VERFUEGBAR and you already
        know from an earlier product lookup that it is available online, suggest buying it
        online instead and include a link to the product page if you have one.

        NOT FOR: click & collect / express pickup or same-day delivery eligibility (not covered
        by this tool), or repeatedly polling a store's stock over time.

        ERRORS: validation error if any DAN is invalid, dans is empty, more than 10 dans are
        given, storeIds is empty, or more than 5 storeIds are given.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dansYesDANs (dm product numbers) (1-10)
storeIdsYesStore IDs of the physical dm stores (1-5)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark the tool readOnly, idempotent, and non-destructive. The description adds substantial behavioral context beyond that: what each status means (especially NUR_ONLINE being store-independent), that made-up storeIds yield STORE_UNBEKANNT, that availability must not be extrapolated across products, and that stockLevel is included in VERFUEGBAR.

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 long but every section earns its place: USE WHEN, INPUT, OUTPUT, IMPORTANT, TIP, NOT FOR, ERRORS. It is front-loaded with the core purpose, and the structured sections make the density navigable rather than rambling.

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?

With no output schema, the description fully documents the return statuses and their meanings, including stockLevel and the NUR_ONLINE caveat. It also enumerates validation error conditions, prerequisite tool usage, and post-result recommendation behavior, making the tool safely callable end-to-end.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaning the schema lacks: valid count ranges (1-5 storeIds, 1-10 DANs), the rule that storeIds must be resolved via findNearbyStores, and how invalid or unknown parameter values map to output statuses. This goes well beyond the schema's terse property descriptions.

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 opens with a specific verb-resource statement: 'Check whether one or more dm-drogeriemarkt products are available in one or more specific stores right now.' It clearly distinguishes itself from siblings by defining its scope, and the 'NOT FOR' line explicitly rules out adjacent use cases like click & collect.

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' guidance, states what it is 'NOT FOR', and gives a hard prerequisite: storeIds MUST come from findNearbyStores and must never be invented. It also instructs when to suggest online buying instead, giving the agent concrete decision rules.

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
Disambiguation4/5

Each tool has a clear primary purpose: searching products, retrieving detailed product info, rendering product cards, finding nearby stores, and checking in-store availability. Minor overlap exists between searchProducts and getProductDetails on ingredient-level answers, but the descriptions clearly delineate full ingredient/allergen details from highlighted attributes.

Naming Consistency5/5

All tool names follow a consistent verb-noun camelCase pattern (findNearbyStores, getProductDetails, getStoreAvailability, renderProductTiles, searchProducts). The verbs vary but are appropriate to each action, and there is no mixing of naming styles or conventions.

Tool Count5/5

Five tools is a well-scoped count for a retail/drugstore information server. Each tool covers a distinct need—search, product details, visual presentation, store location, and availability—without redundancy or unnecessary bloat.

Completeness4/5

The tool set covers the core retail information workflows: searching, full product details, visual product tiles, nearby store lookup, and in-store stock checks. Minor gaps exist (e.g., no direct store lookup by storeId alone, no click-and-collect or ordering support), but these are outside the clearly stated scope of the server.

Resources