Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Cumulus card

get_cumulus_status
Read-only

Retrieve your Cumulus loyalty status, including points collected this period, card number, cardholder, and memberships such as Famigros; requires authentication.

Instructions

Get the user's Cumulus loyalty card: points collected this period, Cumulus number, cardholder and memberships (such as Famigros). 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_status"
  }
}

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 and openWorldHint, so the safety profile is covered. The description adds the authentication requirement, which is real value not present in the annotations, but says nothing about failure modes (e.g., no card on file) or freshness of the points balance.

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?

Two clauses, front-loaded with the resource and then the returned fields, with the authentication caveat trailing. No filler or restatement of the title.

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?

A zero-parameter read tool with annotation coverage needs little, and the description compensates for the absent output schema by naming the returned fields. Only the empty/error case (user has no Cumulus card) is left unaddressed.

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 no parameters, so the baseline is 4; the description correctly implies no input is needed and spends its words on the returned fields instead.

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 ('Get the user's Cumulus loyalty card') and enumerates exactly what is returned: points this period, Cumulus number, cardholder, memberships. That content list implicitly separates it from get_cumulus_bons and get_cumulus_coupons, though no sibling is named explicitly.

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?

Provides one useful precondition ('Requires authentication') but no when-to-use/when-not guidance and no pointer to alternatives such as get_cumulus_coupons for coupon data. Usage is only implied by the tool's purpose.

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