webhallen-mcp

Browse a Webhallen category

list_category

Browse a Webhallen product category by numeric ID or Swedish name, then sort and filter results by price, brand, stock, and other facets to refine product listings.

Instructions

Browse a product category by numeric id or by name (e.g. 'Intern M.2 SSD', 'Grafikkort'). Category names are Swedish; ids show up in search_products facets. Sorted and filterable like search, with brand facets to help refine.

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": {
      "category": "<category>"
    },
    "name": "list_category"
  }
}

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
`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
`category`	Yes	Category id (e.g. '3002') or name (e.g. 'Grafikkort')
`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

A3.8/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Browse' conveys read-only intent and it usefully signals that results carry brand facets for refinement, plus sorting/filtering parity with search, but it says nothing about pagination limits, permission/auth needs, or the shape of a result page.

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 dense sentences, front-loaded with the resource and identifier forms, then the localization caveat, then the filter/sort parity. Nothing is redundant and every clause carries information.

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?

For a read-only browse tool with a fully documented 7-parameter schema and no output schema, the description covers identifier formats, localization, and available refinement. The main residual gap is that it never characterizes the returned listing (pagination is only in the schema), which an agent would want before looping pages.

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 description coverage is 100%, covering category id/name, page size, sort enum, brands, inStock, and price bounds, so the schema already does the heavy lifting. The description adds only the origin of category ids and the fact that filters mirror search; it does not explain semantics the schema omits.

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?

Specific verb+resource ('Browse a product category') with the accepted identifier forms spelled out, which separates it from search_products's keyword query model. It stops short of explicitly naming search_products or get_product as the alternatives, so the sibling boundary is implied rather than stated.

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?

Gives a concrete discovery path ('ids show up in search_products facets') and states that names are Swedish, which is actionable setup guidance an agent would otherwise have to guess. It does not say when to prefer a keyword search or a direct get_product lookup instead, so no exclusion rules are provided.

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

Deploy Server