Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Receipt link

get_receipt_details
Read-only

Get the Migros receipts page link for a given receipt ID so users can sign in and view that receipt's line items; line items aren't available via the server.

Instructions

Get the link to the receipts page on migros.ch, where the user can open a receipt and see its line items. The link is the same for every receipt: line items aren't available to this server. get_in_store_receipts gives store, date, amount and points, enough for most questions. 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": {
      "receiptId": "<receiptId>"
    },
    "name": "get_receipt_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptIdYesReceipt id from get_in_store_receipts.

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 only cover read-only and open-world characteristics; the description adds that the returned link is identical for every receipt and that authentication is required. That is genuine behavioral context the annotations don't carry, though it doesn't describe what the link response itself looks like.

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?

Four tight sentences, front-loaded with purpose, then the limitation, then the alternative tool, then the auth requirement. No redundancy or filler.

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?

Without an output schema, the description still explains the return value (a URL), the auth prerequisite, and the key limitation that line items aren't available to this server. Nothing critical for a single-parameter read tool 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?

Schema coverage is 100% and the receiptId field is already documented as coming from get_in_store_receipts, so baseline is 3. The description goes further by revealing that the parameter has no effect on the resulting link ('the same for every receipt'), which meaningfully shapes how an agent uses it.

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 ('Get the link to the receipts page on migros.ch') and immediately clarifies what the link enables (opening a receipt to see line items). It also explicitly differentiates from the sibling get_in_store_receipts, so an agent can distinguish them 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 Guidelines4/5

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

Names the alternative, get_in_store_receipts, and explains that it supplies store, date, amount and points, 'enough for most questions' — implying this tool is the fallback for line-item views. The routing condition is clear but stated indirectly rather than as an explicit 'use this when' clause.

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