Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Cumulus bons

get_cumulus_bons
Read-only

Lists a signed-in user's Cumulus bons—vouchers converted from Cumulus points—so they can be redeemed at checkout on migros.ch or in a Migros store. Read-only and requires authentication.

Instructions

List the user's Cumulus bons (vouchers their Cumulus points turned into). Read only: bons are redeemed at checkout on migros.ch or in a store. Requires authentication.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/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 "Read only" is largely redundant. The description does add two genuine pieces of behavioral context beyond the annotations: the tool returns only the calling user's bons, and it "Requires authentication" — an operational prerequisite not encoded anywhere else. It says nothing about ordering, pagination, or whether expired/redeemed bons are included.

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?

Three short sentences, front-loaded with the verb and resource, with the explanatory gloss immediately after. Only waste is "Read only", which duplicates the readOnlyHint annotation and could be dropped in favor of more useful return-scope detail.

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

Completeness5/5

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

For a no-parameter, read-only list tool with no output schema and annotations already covering the safety profile, the definition supplies what remains needed: what a bon is, whose bons are returned, and that authentication is required. Nothing essential to calling it correctly is missing.

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?

The tool takes zero parameters, so there is no parameter semantics to document; the baseline of 4 applies. The description correctly frames the result as scoped to "the user's" bons, which is the one implicit input (identity) an agent should understand.

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 ("List the user's Cumulus bons") and parenthetically explains what a bon is ("vouchers their Cumulus points turned into"), which an agent cannot infer from the name alone. It stops short of distinguishing bons from the sibling get_cumulus_coupons, so the boundary between those two resources 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?

Usage is only implied: the phrase "vouchers ... redeemed at checkout" suggests this is for reviewing redeemable vouchers, but there is no explicit when-to-use statement, no when-not-to-use, and no pointer to get_cumulus_coupons for the closely related case.

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