Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Stock at a store

get_stock
Read-only

Check approximate product stock at a specific Migros store using product and store IDs found through product and store search.

Instructions

Check product stock at a specific Migros store. Use search_products and search_stores first to get the IDs. Stock is approximate and updated once a day.

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": {
      "productId": "<productId>",
      "storeId": "<storeId>"
    },
    "name": "get_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeIdYesStore ID (costCenterId) to check stock at. Get this from search_stores.
productIdYesProduct UID to check stock for. Get this from search_products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds value beyond them by disclosing that stock figures are approximate and refreshed only once a day — a material caveat for interpreting results that no structured field provides.

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?

Three short, front-loaded sentences with zero filler: the purpose comes first, the prerequisite second, and the data-quality caveat last. Nothing could be cut without losing information.

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

Completeness4/5

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

For a two-parameter read tool with full schema coverage and annotations, the description covers purpose, prerequisites, and the freshness caveat. It stops short of describing the result shape (availability flag vs. quantity), which matters slightly since there is no output schema.

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%: both productId and storeId already document their format and their source (search_products / search_stores). The description's 'specific Migros store' phrasing adds only marginal meaning, so the baseline 3 applies.

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?

States a specific verb and resource ('Check product stock') plus the scope ('at a specific Migros store'), which cleanly separates it from search_products/search_stores that only return IDs. An agent can tell exactly what this tool returns conceptually without opening the schema.

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

Usage Guidelines4/5

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

Explicitly tells the agent to call search_products and search_stores first to obtain the required IDs, which is the key precondition for using this tool. It does not state when NOT to use it (e.g. bulk stock checks across many stores), so it falls short of full when/when-not guidance.

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