alza-mcp

Overview Schema Source Related Servers Discussions Admin

List delivery & payment options

delivery_options

Read-onlyIdempotent

List delivery and payment options for the cart to display available choices and return the selected delivery option ID required for checkout.

Instructions

List the delivery and payment option groups for the current Alza account cart (AlzaShop pickup, AlzaBox lockers, courier, payment methods) from the mobile API. Use after items are in the cart and before checkout_preview, to show the user delivery/payment choices and to obtain the selected_delivery_option_id that later steps may require. Do not use on an empty cart — Alza answers with validation errors. Pass selected_delivery_option_id to re-fetch the groups anchored on a specific delivery choice. Requires a loaded mobile API access token — check account_status first; if none is loaded, run auth_start, have the user complete the browser sign-in, then auth_exchange with the returned code and state. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`selected_delivery_option_id`	No	Delivery option id from a prior response to anchor the group listing on a chosen delivery method. Omit for the default listing.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`err`	No
`msg`	No
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds substantial behavior beyond annotations: it states the operation is read-only, warns about validation errors on an empty cart, and provides a full authentication prerequisite flow. This goes well beyond the readOnlyHint/idempotentHint annotations and helps an agent avoid failed calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main purpose is front-loaded and each sentence carries substantive guidance. The auth flow is detailed and useful, though the overall text is a bit long relative to the one-parameter schema; still, there is no wasted or redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one optional parametereb and an output schema, this description covers the required prerequisites, error conditions, parameter behavior, and relationship to later steps. Nothing needed to invoke it correctly is left undocumented.

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?

The schema already provides 100% coverage for the single optional parameter, including meaning and default behavior. The description repeats this information without adding new semantic detail, so the baseline score of 3 is appropriate.

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?

The description opens with a clear verb and resource: 'List the delivery and payment option groups for the current Alza account cart', and enumerates concrete examples (AlzaShop pickup, AlzaBox lockers, courier, payment methods). It also identifies the source API and is easily distinguishable from siblings like checkout_preview or payment_methods.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use guidance is given: 'Use after items are in the cart and before checkout_preview'. It also gives a strong when-not-to-use rule: 'Do not use on an empty cart — Alza answers with validation errors', plus instructions for anchoring on a previously selected delivery option.

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