Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Sign in to Migros

authenticate
Idempotent

Log in to Migros with a current six-digit authenticator code when an authenticated action requires a fresh code; omit the code to reuse a cached session or if no 2FA is configured.

Instructions

Log in to Migros with the current six-digit 2FA code from the user's authenticator app (ask the user for it). Only needed when an authenticated tool reports fresh_code_required, which happens when no TOTP secret is configured. Omit totpCode to reuse a cached session, or if the account has no 2FA. The code is never stored or returned.

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": "authenticate"
  }
}

Input Schema

NameRequiredDescriptionDefault
totpCodeNoCurrent six-digit TOTP code. Omit to reuse a cached session, or if the account has no 2FA.

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 declare a non-read-only, non-destructive, idempotent, open-world operation, and the description adds genuinely useful behavior beyond that: the code is never stored or returned, and omitting it reuses a cached session. It stops short of describing failure behavior for an invalid or expired code, which would matter for a login flow.

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 tight sentences with the action first, the trigger second, and the parameter shortcut third. Every clause carries information an agent needs; nothing is redundant padding.

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 one optional parameter, no nesting, and no output schema, the definition covers everything required to call the tool correctly, including credential sourcing and caching. The only omission is what a successful call returns or how failures surface, which is minor for a single-parameter login helper.

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 description coverage is 100% and the single parameter already carries its own description, so the baseline is 3. The description reinforces the omission semantics and the six-digit shape, but adds no format or sourcing detail beyond what the schema states.

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 opens with a specific verb and resource ('Log in to Migros') and narrows it to credential acquisition via a six-digit 2FA code. It is unmistakably an authentication tool, clearly separable from the shopping/catalog siblings, and even names the triggering condition (fresh_code_required).

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?

It states exactly when the tool is needed ('Only needed when an authenticated tool reports fresh_code_required, which happens when no TOTP secret is configured') and when not to call it with a code ('Omit totpCode to reuse a cached session, or if the account has no 2FA'). The agent also learns to ask the user for the code rather than invent one.

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