Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Find stores

search_stores
Read-only

Find Migros stores by city name or ZIP code, including store addresses and opening hours.

Instructions

Find Migros stores by location (city name, zip code, etc.). Returns store details including address and opening hours.

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_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query for Migros stores (city name, zip code, etc.)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior3/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 and open-world profile is covered. The description adds real value by naming the return payload (address and opening hours), but says nothing about result volume, matching behavior, or handling of unmatched queries.

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 short sentences with zero filler; the lookup scope is front-loaded and the return-value note follows immediately. Nothing redundant or padded.

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 one-parameter, read-only lookup with annotations covering safety and no output schema, the description supplies the two things an agent needs: how to search and what comes back. Only mild gaps remain around result-set behavior (multiple matches, no-match case).

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% for the single `query` parameter, and the description's phrasing ("city name, zip code, etc.") essentially mirrors the schema. No additional syntax, format, or matching-semantics detail is provided beyond the structured field, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Find") and resource ("Migros stores") plus the lookup key ("by location (city name, zip code, etc.)"). The resource name alone separates it from search_products and search_recipes, but it never explicitly distinguishes itself from sibling lookups like get_stock or get_addresses.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when it needs a store address or opening hours, but there is no explicit when-to-use statement, no prerequisites, and no mention of what to do when a location query is ambiguous or returns multiple stores.

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