webhallen-mcp

Search Webhallen products

search_products

Search Webhallen’s product catalog by keyword in Swedish or English to find products with prices in SEK, sale details, ratings, availability, and URLs; filter by brand, price, and stock.

Instructions

Search the Webhallen catalog by keyword (Swedish or English). Returns products with price (SEK), sale info, rating, availability and URL, plus brand/price/category facets and nextPage for paging. Filters are applied server-side.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number, 24 products per page
`sort`	No	Sort order: relevance (default), popularity, price_asc, price_desc, rating, newest, discount	relevance
`query`	Yes	Search keywords, e.g. 'nvme ssd 2tb' or 'mekaniskt tangentbord'
`brands`	No	Only these manufacturers (exact names as shown in the brands facet), e.g. ['Samsung', 'Kingston']
`inStock`	No	Only products in stock: 'web' for online orders, or a store id from list_stores
`maxPrice`	No	Maximum price in SEK
`minPrice`	No	Minimum price in SEK

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden; it does disclose that filters are applied server-side and that paging uses nextPage, which is useful. However, it says nothing about rate limits, authentication requirements, error behavior, or result-count limits beyond the schema's 24-per-page note. For a filter-heavy search tool with zero annotation coverage, that leaves meaningful gaps.

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

Conciseness5/5

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

Three tight sentences with no filler: purpose first, return shape second, server-side filtering last. Every clause carries information an agent can act on.

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?

With no output schema, the description compensates well by enumerating the returned fields and the paging mechanism, and all seven parameters are documented in the schema. It falls just short of full completeness because failure modes (no results, invalid store id) and any rate or auth constraints are unaddressed.

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%, so every parameter is already documented with examples and enums, making the baseline 3 appropriate. The description adds only indirect value by mentioning brand/price/category facets, which confirms that brand and price filters are backed by facet data, but it does not explain how to harvest facet values or how inStock interacts with list_stores beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Search the Webhallen catalog by keyword') and enumerates what comes back (price, sale info, rating, availability, URL, facets). It is clearly a catalog search rather than a single-item lookup, but it never names a sibling (e.g. get_product, list_category) to delimit itself.

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

Usage Guidelines2/5

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

There is no when-to-use guidance — nothing explains when to search by keyword instead of browsing list_category or comparing via compare_products. The only contextual hint is the parenthetical '(Swedish or English)' about query language, which is a usage note but not routing guidance.

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

Deploy Server