Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Product details

get_product_details
Read-only

Retrieve full product details—including nutrition facts, ingredients, allergens, price, and ratings—for product IDs obtained from a prior product search.

Instructions

Get full product details including nutrition facts, ingredients, allergens, price, and ratings. Use search_products first to get product IDs.

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": {
      "productIds": "<productIds>"
    },
    "name": "get_product_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdsYesArray of product IDs (UIDs) to get details for. Get these from search_products first.

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds value beyond them by disclosing the shape of the response (nutrition, ingredients, allergens, price, ratings), which matters because there is no output schema. It does not address behavior for invalid or unknown product IDs.

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 sentences, zero waste. The capability statement comes first and the prerequisite second, which is the correct front-loading for an agent deciding whether to call it.

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?

For a one-parameter read tool with annotations present and no output schema, the description is nearly complete — it names the returned fields and the ID prerequisite. The only gap is what happens when an ID resolves to nothing, which is minor for this complexity.

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 parameter already documents the ID array, its pattern, and the maxItems=50 cap. The description only echoes the schema's "get these from search_products first" note, adding no format or constraint detail beyond it, 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?

States a specific verb and resource ("Get full product details") and enumerates the returned content: nutrition facts, ingredients, allergens, price, ratings. This is far more specific than the title and lets an agent distinguish it from retrieval siblings like get_stock or get_recipe_details.

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?

"Use search_products first to get product IDs" gives an explicit prerequisite and names the alternative that produces the required input. It stops short of exclusions — nothing says when to prefer get_stock or get_recipe_products instead — but the sequencing guidance is clear.

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