Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Checkout link

get_checkout_link
Read-only

Returns the browser URL needed to complete checkout, including basket review, address and slot confirmation, and payment. Use it to hand off order placement to a real browser session.

Instructions

Return the URL the user should open in their browser to complete checkout (review basket, confirm address/slot, pay). Order placement requires payment confirmation in a real browser, so this tool hands off rather than firing the order automatically. Returns a basket summary alongside the URL. 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_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
shoppingListIdNoOptional shopping list ID from get_shopping_lists. Omit to use the first list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the supplied readOnlyHint/openWorldHint annotations, the description discloses three useful behaviors: authentication is required, the call does not place the order, and a basket summary is returned alongside the URL. That is meaningful context for an open-world read tool; only things like URL expiry or whether the link is single-use are 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 sentences, none wasted: the action and return value come first, the rationale for the handoff second, and the auth prerequisite last. Every sentence contributes distinct information.

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 only one optional parameter, no output schema, and safety already covered by annotations, the description covers essentially everything an agent needs to invoke it correctly. Minor gaps remain around link lifetime/validity and whether the basket summary format is stable.

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 optional shoppingListId is fully described in the schema, including its default behavior when omitted. The description adds no extra meaning about the parameter, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Return the URL the user should open in their browser to complete checkout') and immediately delimits it from a hypothetical order-firing tool by calling it a handoff. No sibling in the list performs checkout, so the agent can identify this as the single checkout entry point without further inspection.

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?

It is clear when to use this tool: when the user needs to complete checkout in a browser, and it explains why the tool cannot itself place the order. It does not name sibling alternatives or explicit exclusions, but the context makes the boundary self-evident (all other siblings are read/cart-mutation tools).

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