alza-mcp

Overview Schema Source Related Servers Discussions Admin

Read a raw Alza mobile API operation

mobile_read

Read-onlyIdempotent

Execute Alza mobile API read operations for data without a dedicated tool, such as product details, alternatives, or order info. Provide operation and args to get the raw API response.

Instructions

Read-only escape hatch for Alza mobile API operations that have no dedicated tool. Prefer the typed tool when one exists — cart (operation basket_info), profile (user_data), contacts (contacts), search_products (search), list_categories (category), order (user_order) — and use mobile_read for the rest. High-value operations: router_product {product_id} returns the full product envelope including the parameterGroups spec sheet (product_id is the numeric d######## id from the product URL, e.g. 13078770 from https://www.alza.cz/...-d13078770.htm); legacy_product {product_id, ucik, pgrik, country} is the same with the server-required UCÍK/PGŘÍK values (copy them from a router_product response); also alternatives {product_id}, ean_lookup, facets, hierarchical_filter, commodity_list(s), cost_estimate, delivery_countries, web_after_payment_dialog {order_id}, order_part/order2_info {order_id, ...}, order_helpdesk_questions, user_review, discussion_posts, premium_trial, validate_login_name, validate_isic, o3_info, quick_order_summary, home_categories (requires the server-side pgri/ui query values — copy them from an upstream self href in a navigation response, e.g. ?pgri=p__…&ui=u__…), zip_codes/web_zip_codes, branches, visitor_navigation/user_navigation/catalog_user_navigation, anonymous_orders/anonymous_order, url_info. This tool never accepts arbitrary URLs or credentials, and never mutates state. Account-scoped operations 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. Returns the raw upstream envelope (err/msg/data); err:1 with a msg is an Alza-side validation (e.g. unknown product id).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`args`	No	Operation-specific arguments as a JSON object, e.g. router_product: {product_id: 13078770}; web_after_payment_dialog: {order_id: "..."}. Omit for operations that take none.
`operation`	Yes	Which fixed, APK-confirmed mobile API read operation to execute. See the tool description for per-operation arguments.

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.8/5.0

Behavior5/5

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

Even though annotations already declare read-only and non-destructive, the description adds substantial behavioral context: it never accepts arbitrary URLs or credentials, never mutates state, requires a loaded token for account-scoped operations, and returns a raw envelope with err/msg/data semantics. This is exactly the kind of disclosure that annotations alone do not provide.

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 description is long but information-dense, with a logical flow: purpose, alternatives, high-value operations, constraints, auth, return semantics. Every sentence adds value, though the flat paragraph format could be improved with bullet points for readability. It is appropriately sized for a catch-all tool covering many operations.

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?

Given the tool's breadth, the description covers everything essential: alternatives, representative operations with arguments, authentication requirements, error semantics, and return envelope shape. It does not document every possible operation's arguments, but for an escape hatch that is acceptable given the enum and output schema exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the schema's argument descriptions are generic. The description goes far beyond by explaining per-operation argument formats, providing concrete examples (e.g., product_id extraction from a URL, ucik/pgrik sourcing), and clarifying which operations take no arguments. This makes parameter semantics genuinely actionable.

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 states a specific verb+resource (read-only escape hatch for Alza mobile API operations) and explicitly distinguishes itself from typed siblings by naming them (cart, profile, contacts, etc.). This is not a tautology and clearly tells an agent what the tool is for.

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?

It gives explicit when-to-use guidance: prefer typed tools when they exist, use mobile_read for the rest. It also details when authentication is required, which auth steps to invoke first, and what error responses mean. The usage context is unambiguous.

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