Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Deactivate Cumulus coupon

deactivate_cumulus_coupon
Idempotent

Reverts an activated Cumulus coupon back to AVAILABLE status using the EAN from get_cumulus_coupons. Requires authentication to remove the coupon from the card.

Instructions

Take an activated Cumulus coupon off the card again (status back to AVAILABLE). 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": "deactivate_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

A3.8/5.0
Behavior4/5

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

Adds real context beyond the annotations: the state transition back to AVAILABLE and the authentication requirement, neither of which the annotations convey. It also implicitly confirms the reversal is non-destructive, consistent with destructiveHint=false and idempotentHint=true; only return-value behavior is left unstated.

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 outcome, then the parameter source, then the auth requirement. Nothing is wasted or 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 tool with full annotations and no output schema, the description covers purpose, outcome state, parameter provenance, and auth. Only the response behavior after deactivation is missing, which is minor given no output schema exists.

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% and the single ean parameter already carries the pattern, required flag, and a description naming get_cumulus_coupons. The description repeats that provenance without adding format or edge-case detail, so 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 and resource ("Take an activated Cumulus coupon off the card again") and names the resulting state (AVAILABLE), which makes it clearly the inverse of activation. It does not explicitly name the sibling activate_cumulus_coupon, but the wording makes the distinction obvious.

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?

Implies the usage condition through "an activated Cumulus coupon" and directs the agent to source the ean from get_cumulus_coupons. It does not state when to prefer this over alternatives or any preconditions beyond authentication, so guidance is only implied.

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