Skip to main content
Glama

get_product_details

Read-onlyIdempotent

Get full details for a single Rakentaja Outlet product.

Fetches both the product record and a real-time availability check in parallel. Use this after search_catalog returns a product ID to show the user complete information (full description, all images, current stock).

Args: product_id: Product ID from search_catalog results (integer).

Returns: JSON with product details: - id, name, sku, ean, brand, category - description (full HTML/text), description_short - price_gross (incl. 25.5% VAT), price_net, vat_percent, currency - available_for_order (bool), availability_status ("in_stock" | "supplier_stock" | "out_of_stock"), estimated_delivery_min_days, estimated_delivery_max_days - in_stock, stock_quantity, supplier_in_stock, supplier_stock_quantity (raw fields — prefer available_for_order + availability_status) - weight_kg, unit - product_url (direct link to product page) - image_url (main image), images (list of all image URLs) - availability: fresh stock check result (may be more current than stock_quantity if inventory changed since catalog was cached) - disclaimer: legal notice that prices are indicative

On error, raises MCP ToolError → response has isError:true with
structured JSON: {"error": {"code": "not_found" | "invalid_argument"
| "backend_unavailable", "message": "...", "field": null|str,
"retryable": true|false}}. The StructuredErrorMiddleware ensures
the format is consistent across all tools.

Notes: - Prices include Finnish 25.5% VAT. Business buyers see price_net for VAT-registered net price. - Pass product_url to the user for viewing or adding to cart — do not attempt to add to cart via this tool (use create_cart_link).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idYesProduct ID from search_catalog results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct ID (use with get_product_details for full info)
eanNo
skuNo
nameYes
unitNokpl
brandNo
imagesNoAll product image URLs
categoryNo
currencyNoEUR
in_stockYes
image_urlNo
price_netYesNet price for VAT-registered business buyers
weight_kgNo
disclaimerYes
descriptionYesFull product description (may contain HTML)
price_grossYesGross price incl. 25.5% Finnish VAT
product_urlYesDirect link to product page — pass this to the user
vat_percentNo
availabilityNoFresh availability check (may be more current than stock_quantity)
stock_quantityYes
description_shortNo
supplier_in_stockYes
availability_statusYesDetailed status: in_stock = own warehouse, supplier_stock = from supplier
available_for_orderYesWhether customer can order this — TRUE if in own stock OR supplier stock available
supplier_stock_quantityYes
estimated_delivery_max_daysNoHitain toimitusarvio arkipäivinä (null = ei saatavilla)
estimated_delivery_min_daysNoNopein toimitusarvio arkipäivinä (null = ei saatavilla)

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds real-time availability fetch, VAT details, error format, and field clarifications (e.g., prefer available_for_order over raw fields). No contradictions with annotations.

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?

Description is well-structured with clear sections (overview, Args, Returns, Notes). Front-loaded with main purpose. Slightly verbose in Returns section but every sentence adds necessary detail. Could be trimmed slightly.

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?

Given schema and annotations, description covers all needed aspects: purpose, usage, parameter, detailed return format, error handling, and practical notes (VAT, not for cart). Output schema exists but description still explains fields. No obvious gaps.

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?

Only one parameter (product_id) with 100% schema coverage. Description repeats schema info ('Product ID from search_catalog results') without adding new meaning about format or constraints. Adequate but adds no extra value beyond schema.

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 clearly states that the tool gets full details for a single product, fetching both product record and real-time availability. It explicitly distinguishes from siblings by stating 'Use this after search_catalog returns a product ID' and warns against adding to cart (use create_cart_link instead).

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?

The description provides explicit guidance: 'Use this after search_catalog returns a product ID to show the user complete information' and 'do not attempt to add to cart via this tool (use create_cart_link)'. This clearly defines when to use and when not to use.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: cart link generation, product details, catalog search, and policy/FAQ search. No overlap or ambiguity.

Naming Consistency5/5

All tools use a consistent verb_noun pattern in snake_case: create_cart_link, get_product_details, search_catalog, search_shop_policies_and_faqs.

Tool Count4/5

With 4 tools, the set is well-scoped for a store assistant. It covers core shopping flows without being bloated. A category listing tool could be a minor addition.

Completeness4/5

Covers product search, details, cart creation, and policies. Missing user account or order management, but these are reasonable omissions for the assistant role.

Resources