Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Current promotions

get_promotions
Read-only

Search current Migros promotions and deals, optionally filtering by a query to surface relevant offers.

Instructions

Search current Migros promotions and deals. Optionally filter by search query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_promotions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional search query to filter promotions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.4/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 profile and the open-ended result set are given. The description adds only the "current" temporal scoping, which is genuinely useful behavior beyond the annotations, but it says nothing about result volume, pagination, ordering, or how promotions are matched to the query.

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?

Two short sentences with the primary capability front-loaded and the parameter note second; nothing is redundant. It is slightly sparse rather than padded, so brevity is not costing clarity here, but there is room for one more sentence of routing or behavior detail.

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

Completeness3/5

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

For a one-optional-parameter read tool with no output schema, the description covers purpose and parameter behavior adequately, and the guidance that return values need not be explained applies. However, an agent still lacks any hint about result size or how promotions are scoped (per store, per region, national), which matters given openWorldHint=true.

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% and the single parameter (query) is fully documented in the schema, so the baseline is 3. The description's "optionally filter by search query" only restates that the parameter is optional and filtering-oriented, adding no matching semantics (e.g., substring vs. keyword, accent/locale handling) beyond the schema.

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?

The description gives a concrete verb and resource ("Search current Migros promotions and deals") plus the scope qualifier "current," so an agent knows this returns time-sensitive promotional content rather than catalog products. It does not explicitly contrast itself with search_products or get_categories, which could plausibly surface overlapping merchandising data, so sibling differentiation is left implicit.

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?

"Search current Migros promotions and deals" implies the use case of looking up active discounts, and "Optionally filter by search query" clarifies that the call works with no arguments. There is no explicit statement of when to prefer this over search_products or when not to use it, and no mention of what happens if the user wants historical or expired promotions.

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