Skip to main content
Glama

search_shop_catalog

Read-onlyIdempotent

Search Rakentaja Outlet product catalog.

Rakentaja Outlet (rakentajaoutlet.fi) is a Finnish online store specializing in electrical and construction supplies at outlet prices (~4000 products). All prices in EUR including 25.5% Finnish VAT.

Args: query: Free-text search — matches product name, SKU, EAN code, or category name. Leave empty to browse without a search term. category_id: Filter to products in a specific category (integer ID). The full list of categories is available at https://rakentajaoutlet.fi/api/categories — this is a public REST endpoint, not an MCP tool. Combines with query if both given. in_stock_only: If True (default), only show products currently in stock (either in own warehouse or at supplier). Set to False to include out-of-stock products in results. sort: Sort order — "name" (default), "price_asc", "price_desc", or "newest". Ignored when query is given; search results are ordered by relevance instead. limit: Maximum products to return (1-50, default 10). Use a small limit for interactive queries; larger for bulk listing. page: Page number for paginated results (default 1). Combine with limit to page through results larger than the limit.

Returns: JSON with keys: - products: list of product summaries with: - id, name, category, brand, sku, ean, unit - price_gross (incl. 25.5% VAT), price_net, currency - description (max 200 chars, description_truncated=true for longer) - available_for_order: boolean — can the customer place an order? (TRUE if in own stock OR supplier stock available) - availability_status: "in_stock" | "supplier_stock" | "out_of_stock" - estimated_delivery_min_days / _max_days: delivery estimate (or null) - in_stock, stock_quantity, supplier_in_stock, supplier_stock_quantity (raw fields — prefer available_for_order + availability_status) - product_url, image_url - total: total matching products across all pages - page: current page number - per_page: products per page (== limit) - total_pages: total pages available - disclaimer: legal notice that prices are indicative and confirmed at checkout

Notes: - Prices include Finnish 25.5% VAT (price_gross) and net price (price_net) is shown for VAT-registered business buyers. - product_url is a direct link to the product page — pass this to the user for viewing or adding to cart. - Use get_product_details(id) for full description and stock check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (>= 1)
sortNoname
limitNoMax products to return (1-50)
queryNoFree-text search term
category_idNoCategory ID (see https://rakentajaoutlet.fi/api/categories for the list)
in_stock_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
totalYesTotal matching products across all pages
per_pageYes
productsYes
disclaimerYes
total_pagesYes
suggested_queriesNoAlternative queries that would return results — populated when total=0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive; description adds substantial behavior: searchable fields match name/SKU/EAN/category, sort ignored when query is given, stock availability semantics, VAT handling, truncated descriptions, and legal disclaimer. No contradiction; provides rich context beyond 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?

Long but well-structured with Args, Returns, and Notes sections; every section carries actionable details. Some redundancy (VAT appears in intro and Notes) but overall efficient for a 6-parameter search tool with a rich response.

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?

Covers domain, pricing/VAT, filtering, pagination, availability, product links, and cross-reference to get_product_details. Though an output schema exists, the description adds field semantics and caveats, making the tool safely invocable in isolation.

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?

The Args section expands every schema parameter with richer meaning: query matches multiple fields, category_id references an external public endpoint, in_stock_only explains stock sources, sort details ignored-under-query behavior, and limit/page include usage guidance. This materially exceeds the schema's brief descriptions.

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?

Description opens with 'Search Rakentaja Outlet product catalog,' naming the specific retailer, domain, and action. It further characterizes the store as Finnish outlet for electrical/construction supplies, clearly distinguishing it from generic search siblings.

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?

Provides explicit operational guidance: when to leave query empty, pagination strategy, sorting behavior when query is given, and points to get_product_details(id) for full description/stock. Does not explicitly exclude sibling search_catalog, but context makes its purpose clear.

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