Systembolaget API MCP Server

Overview Schema Source Related Servers Discussions Admin

search_products

Search Systembolaget products by launch date range, automatically fetching all pages and returning combined results.

Instructions

Search Systembolaget (Swedish liquor store) products by product launch date range. Fetches all pages automatically and returns the combined result.

Returns products that have a launch date between launch_date_min and launch_date_max. By default returns a compact response (metadata + key product fields only). Set full_response=True to get the complete API-style response (all fields, filters, etc.).

Args: launch_date_min: Start of launch date range (YYYY-MM-DD). Maps to productLaunch.min. launch_date_max: End of launch date range (YYYY-MM-DD). Maps to productLaunch.max. size: Page size used when fetching (default 100). All pages are fetched automatically. sort_by: Sort field (e.g. "Score"). Default "Score". sort_direction: "Ascending" or "Descending". Default "Ascending". assortment_text: Assortment filter (e.g. "Tillfälligt sortiment"). Default "Tillfälligt sortiment". full_response: If False (default), return only metadata and key product fields for speed. If True, return the full response structure (all fields, filters, etc.).

Returns: By default: metadata (docCount, totalPages, nextPage, previousPage) and products with productId, productNameBold, productNameThin, producerName, price, volume, volumeText, alcoholPercentage, country, categoryLevel1, customCategoryTitle, assortmentText, productLaunchDate, taste, usage, vintage. If full_response=True, the complete response with all products and filters is returned.

Input Schema

TableJSON Schema

Name	Required	Default
`size`	No
`sort_by`	No	Score
`full_response`	No
`sort_direction`	No	Ascending
`assortment_text`	No	Tillfälligt sortiment
`launch_date_max`	Yes
`launch_date_min`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does reasonably well: it discloses that all pages are fetched automatically, that the response defaults to a compact form, and enumerates what the compact form contains. It omits auth requirements, rate limits, and behavior on empty/invalid ranges, 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.

Conciseness4/5

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

Well front-loaded (purpose and date-range semantics first, then Args and Returns) and each section is useful. It is somewhat verbose – the Returns block repeats fields the output schema likely already defines – but nothing is padding.

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 7-parameter paged search tool with no annotations, the description covers parameters, pagination, defaults, and return shape, which is enough to invoke it correctly. The one real gap is that it never positions the tool against its sibling or states when not to use it.

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?

Schema description coverage is 0%, so the description must compensate, and it does: every one of the 7 parameters is documented with type, default, accepted values, and even the upstream field mapping (launch_date_min -> productLaunch.min, YYYY-MM-DD format). This is far beyond what the bare schema provides.

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?

States a specific verb and resource ('Search Systembolaget products') plus the scoping dimension (launch date range) and a notable behavior (automatic pagination). It does not, however, distinguish itself from the sibling list_products_formatted, so an agent cannot tell from the description alone which of the two to pick.

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

Usage Guidelines3/5

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

Usage is implied by the required date-range parameters, and the description does guide the full_response=True vs default choice. But there is no explicit when-to-use / when-not-to-use statement and no mention of the alternative list_products_formatted.

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

Deploy Server