Skip to main content
Glama

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.

  1. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

The description thoroughly explains output statuses (VERFUEGBAR, NICHT_VERFUEGBAR, NUR_ONLINE, etc.) and their meanings, including nuanced cases like NUR_ONLINE being store-independent. It also describes error conditions and required workflow (call findNearbyStores first), going well beyond what annotations provide.

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?

The description is well-structured with clear sections (USE WHEN, INPUT, OUTPUT, IMPORTANT, NOT FOR, ERRORS). However, it is somewhat lengthy and repeats similar warnings about not extrapolating results, which could be more concise.

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 absence of an output schema, the description fully explains return values and their meanings, error conditions, and the necessary workflow. It covers all aspects an agent needs to invoke and interpret the tool correctly.

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?

Even though schema coverage is 100%, the description adds crucial constraints: storeIds must come from findNearbyStores, and dans are dm product numbers with limits (1-5 storeIds, 1-10 dans). It also emphasizes passing all products in one call rather than making separate requests.

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 states a specific verb (check availability), resource (dm-drogeriemarkt products), and scope (specific stores, right now). It clearly distinguishes itself from siblings like findNearbyStores, which is named as a prerequisite.

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?

It provides explicit USE WHEN and NOT FOR sections, identifies the required alternative (findNearbyStores), and warns against misuse such as inventing storeIds or assuming product availability.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources