Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Search products

search_products
Read-only

Search Migros products by name or keyword, including Online-only Partner items, and return product IDs for retrieving details or adding items to a basket.

Instructions

Search Migros products by name or keyword, including products sold only in the Migros Online shop (such as 'Partner' products). Returns product IDs that can be used with get_product_details and add_to_basket.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query for Migros products
languageNoLanguage for results (de, fr, it, en). Default: dede

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 the safety profile is covered. The description adds non-obvious coverage information (online-shop-only products are included) and the return type (product IDs), which the annotations do not convey. Pagination or result-count limits remain undisclosed.

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?

Two tight sentences: the first defines what is searched and its scope, the second defines the output and downstream usage. Nothing is redundant and the most important constraint is front-loaded.

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-only search with no output schema, the description covers purpose, scope, and the shape of the result. The only real gap is result-set behavior (limits, paging), which an agent would want before assuming it can enumerate all matches.

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 coverage is 100%, with both query and language documented in the schema including the default and allowed language codes. The description only loosely reinforces that query is a name/keyword and says nothing about language, so it adds little beyond the schema. 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 (search Migros products) plus a distinguishing scope detail: it includes online-only 'Partner' products. The resource noun alone separates it from search_recipes, search_stores, and the get_* detail tools.

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?

The second sentence makes the intended workflow explicit — search first, then feed the returned IDs to get_product_details or add_to_basket — which tells the agent exactly when this tool is the entry point. It stops short of naming when-not to use it or what to do if the query returns nothing.

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