Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Your profile

get_profile
Read-only

Retrieve the logged-in customer's basic profile, including name, email, language, and cooperative, to support authenticated account views.

Instructions

Get the logged-in customer's basic profile (name, email, language, cooperative). 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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely new context the annotations do not contain — the authentication requirement — and hints at the payload shape by naming the four basic fields, though it does not say what happens on an unauthenticated call (error vs empty result).

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?

One sentence plus a short prerequisite clause; both earn their place. The operation and its scope are front-loaded, and there is 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?

With no output schema, the description usefully enumerates the returned fields, which is the main thing an agent would otherwise have to discover by calling. The auth prerequisite is stated. Minor gap: nothing is said about failure behavior when unauthenticated or whether values like 'cooperative' are identifiers versus names.

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?

There are zero input parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The field list in the description refers to the response, not to inputs, and does not create confusion about parameter usage.

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 ('Get') and a precisely scoped resource ('the logged-in customer's basic profile'), then enumerates exactly which fields that profile contains (name, email, language, cooperative). No sibling such as get_addresses or get_orders can be confused with this, since the scope is explicitly the logged-in customer's identity data.

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 gives a clear precondition for use: 'Requires authentication', which tells the agent it must call authenticate first. It offers no exclusions or alternative-tool routing, but no sibling in the catalog retrieves the customer's own profile, so the missing exclusion clauses cost little.

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