Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

In-store receipts

get_in_store_receipts
Read-only

Lists in-store Migros receipts (Kassenbons) for a date range. Returns store, date, amount and points; requires sign-in. Defaults to the last 30 days unless start and end dates are set.

Instructions

List the user's in-store Migros receipts (Kassenbons) over a date range. Default: the last 30 days, Swiss time. Gives store, date, amount and points; line items aren't available to this server (get_receipt_details gives the link to see them on migros.ch). 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_in_store_receipts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax receipts to return. Default: 50.
endDateNoEnd date YYYY-MM-DD. Default: today.
startDateNoStart date YYYY-MM-DD. Default: 30 days ago.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real value on top: authentication requirement, Swiss-time default window, and the exact fields returned (store, date, amount, points). What it omits is truncation/pagination behavior when the limit is hit, which matters for a list tool capped at 500.

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 sentences, front-loaded with the resource and scope, then defaults, then the return shape and the sibling hand-off. Every clause carries information an agent needs; nothing is repeated from the schema verbatim beyond the useful default reminder.

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?

With no output schema, the description correctly compensates by enumerating the returned fields and calling out the notable absence of line items, plus the auth requirement and date defaults. The only gap is what happens when more receipts exist than the limit allows, which an agent cannot infer.

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%, so the baseline is 3; the description earns an extra point by attaching a timezone semantic ("Swiss time") that determines how startDate/endDate are interpreted and is absent from the schema. It does not explain limit behavior beyond what the schema's default and maximum already convey.

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 specific verb and resource ("List the user's in-store Migros receipts") plus the Kassenbons synonym and the date-range scope. The word "in-store" alone separates it from the order-oriented siblings, and get_receipt_details is named as the place for line items, so an agent can discriminate without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this for the receipt list, use get_receipt_details when line items are needed, since they "aren't available to this server." It also states the authentication prerequisite and the default window, so there is no ambiguity about when and how to call it.

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