alza-mcp

Overview Schema Source Related Servers Discussions Admin

Get product details

get_product

Read-onlyIdempotent

Fetches a single Alza product by its Alza code—name, price, availability, rating, brand, category, image, URL, and specs—so you can compare search candidates and retrieve the canonical product link.

Instructions

Fetch details for a single product by its Alza code (the code from search_products, e.g. 'WEXOA002B0' — not the numeric id): name, price (with the original price when discounted), availability, rating, brand, category, primary image, URL, and the spec table when the product page carries one (up to 30 rows, merged from both the DOM spec table and the JSON-LD additionalProperty list some page templates use instead — fixed 2026-09-27 after a product with only the latter returned no params at all). Use after search_products to compare shortlisted candidates in depth, and to get the canonical URL to show the user. For reviews use get_product_reviews; for the complete spec sheet (parameterGroups) use mobile_read with operation=router_product and product_id = the numeric d######## id from the product URL. Sourced from the product page's JSON-LD schema, so values are accurate and stable. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	Alza product code, e.g. 'WEXOA002B0'. This is the canonical identifier returned by `search_products` (the `code` field). Not the numeric id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`product`	Yes	Scraped product detail (JSON-LD sourced; stable fields listed, rest passthrough).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered; the description adds genuinely useful behavioral detail about the return payload (JSON-LD sourced, spec table capped at 30 rows, merged from DOM and JSON-LD additionalProperty). It does not mention rate limits, error behavior, or auth requirements, so it falls short of a 5.

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

Conciseness3/5

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

Front-loaded and information-dense, but it carries dead weight: the parenthetical changelog ('fixed 2026-09-27 after a product with only the latter returned no params at all') is release-note noise that does not help an agent decide or invoke, and the enumerated return fields duplicate the output schema.

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?

An output schema exists, so return values need not be explained, yet the description still lists them — harmless redundancy. Routing, identifier semantics, and alternatives are all present; only edge behavior (errors on unknown code, missing spec table handling) is absent.

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 schema already documents `code` including the 'not the numeric id' warning and the same example. The description largely restates that, so it adds little semantic value beyond the schema — the baseline 3 for a fully documented single parameter.

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+resource ('Fetch details for a single product') and pins the identifier precisely (Alza code from search_products, not the numeric id), with a concrete example. It also names the siblings it is not (search_products, get_product_reviews, mobile_read), so an agent can disambiguate without opening a schema.

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 routing: 'Use after search_products to compare shortlisted candidates in depth', plus two named alternatives with the exact condition selecting each — get_product_reviews for reviews and mobile_read with operation=router_product for the full parameterGroups spec sheet. Nothing is left to inference.

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

Deploy Server