Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Activate Cumulus coupon

activate_cumulus_coupon
Idempotent

Add a personal Cumulus coupon to the user's card by EAN so it applies to their next in-store or online purchase; no purchase is made.

Instructions

Put a personal Cumulus coupon on the user's Cumulus card, so it applies to their next purchase (online or in store). Nothing is bought. Use the ean from get_cumulus_coupons. Requires authentication.

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": {
      "ean": "<ean>"
    },
    "name": "activate_cumulus_coupon"
  }
}

Input Schema

NameRequiredDescriptionDefault
eanYesThe coupon's ean from get_cumulus_coupons.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), so the bar is lower. The description still adds real context beyond them: the effect is deferred to the next purchase, no purchase occurs, and authentication is required — the auth requirement in particular is not encoded in the annotations.

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 sentences, front-loaded with the action and its effect, then the negative boundary, then the prerequisite and auth note. No filler and nothing buried.

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 mutation with no output schema, the description covers effect, boundaries, data source, and auth. The only minor gap is what the caller gets back on success or failure, which is presumably a simple confirmation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single ean field already documents its format and provenance, so the baseline is 3. The description reinforces the source constraint ('Use the ean from get_cumulus_coupons'), which slightly strengthens the link between the two tools but adds little new meaning about the value itself.

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 concrete verb and resource ('Put a personal Cumulus coupon on the user's Cumulus card') and immediately bounds the effect ('so it applies to their next purchase (online or in store)'). The clause 'Nothing is bought' sharply separates it from the basket/purchase siblings, so an agent can identify it 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?

Gives the prerequisite explicitly: 'Use the ean from get_cumulus_coupons', routing the agent to the source tool, and adds 'Requires authentication.' It stops short of naming when NOT to use it (e.g., the deactivate counterpart or an already-activated coupon), so it is clear context rather than 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.