Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Order details

get_order_details
Read-only

Fetch full details for one order by order ID to review order information; obtain the ID from get_orders. Requires authentication.

Instructions

Fetch the full details of a single order by id. Requires authentication.

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": {
      "orderId": "<orderId>"
    },
    "name": "get_order_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYesOrder id (numeric). Get from get_orders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-scope behavior are covered. The description adds one genuinely useful piece of context, "Requires authentication," but says nothing about what "full details" comprises or how it behaves for unknown 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 short sentences, zero filler, with the core action front-loaded and the authentication prerequisite following it. Every clause earns its place.

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 simple single-record read with one fully documented parameter and clear annotations, the definition covers the essentials plus the auth prerequisite. Only minor gaps remain, such as what fields the details include and behavior on an unknown order id.

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?

With a single parameter and 100% schema description coverage, the schema already documents the id format, type union, and that it comes from get_orders. The description's "by id" adds nothing beyond that, so the baseline 3 applies.

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?

"Fetch the full details of a single order by id" gives a specific verb (fetch), a specific resource (one order, not a list), and the lookup key. That implicitly separates it from the sibling get_orders, but it never names the sibling or states the contrast 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?

Usage is only implied: because the tool needs a single order id, an agent infers it must first obtain ids from get_orders (a point the schema makes, not the description). There is no explicit when-to-use, when-not-to-use, or named alternative in the description itself.

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