Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Your orders

get_orders
Read-only

Lists your online orders with status filters and pagination so you can locate an order ID, then retrieve its details. Requires a signed-in account.

Instructions

List the user's online orders, paginated, filtered by status. Use to find an order id, then call get_order_details. 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_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo0-based page number. Default: 0.
statusNoFilter by order status. Default: ALL.

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 the safety profile is covered. The description adds two genuinely useful behavioral facts not in the annotations: it is paginated and it requires authentication. It does not disclose page size, ordering, or what a page of results looks like, which is the remaining gap.

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 short sentences, each carrying a distinct fact: what it returns, how to use it, and the auth prerequisite. Nothing is redundant with the title and no sentence is filler.

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 two-parameter read-only list tool with no output schema and full schema coverage, the description covers purpose, the filter default intent, pagination, auth, and the follow-up call. Only secondary details such as ordering or page size are absent, which is minor at 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 description coverage is 100%, so both page and status are fully documented in the schema including defaults and the enum values. The description only restates that results are paginated and status-filtered, adding no syntax, bounds, or behavioral nuance beyond the schema. 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 ('List the user's online orders') plus the two dimensions that shape the result (pagination, status filter). It also explicitly separates itself from get_order_details, so an agent can pick correctly without opening either schema.

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?

Gives a concrete usage path: use this to locate an order id, then call get_order_details. That is a clear routing instruction naming the sibling that follows. It stops short of stating when NOT to use it (e.g. already holding an id), so it falls just short of the top score.

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