okun-koneosa

Server Details

Finnish industrial supplies store. Read-only MCP: catalog search, product details, cart, policies.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-09-18 03:21
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.3/5.0

Scored 2026-08-05 17:40 across 5 tools

Disambiguation2/5

search_catalog and search_shop_catalog are exact duplicates with identical descriptions and arguments, making it impossible for an agent to distinguish them. The other three tools are distinct, but having two tools that do the same thing creates genuine ambiguity.

Naming Consistency4/5

All tool names follow a consistent verb_noun snake_case pattern (create_, get_, search_). However, the duplicate functionality is named inconsistently (search_catalog vs search_shop_catalog), which is a minor deviation from naming clarity.

Tool Count4/5

With 5 tools the count is within the reasonable range for a shop catalog server. However, one tool is redundant, effectively reducing the unique functionality to 4 tools, which is still acceptable but not ideal.

Completeness4/5

The tool surface covers product search, product details, cart link creation, and policy lookup, which are the core operations for a catalog-driven shop. Minor gaps exist (e.g., no direct category listing) but these are mitigated by external REST endpoints and the tools work together for common workflows.

Available Tools

5 tools

create_cart_linkA

Read-onlyIdempotent

Inspect

Build a link that puts the given products into the customer's cart.

This tool writes nothing. It returns a URL; the products are added only when the customer opens that URL in their own browser. Give the URL to the customer and let them click it.

Args: items: 1-20 rows of {"product_id": int >= 1, "quantity": int 1-50}. Unknown fields are rejected. Repeated product_ids are merged into one row and their quantities summed. checkout: If True, opening the link takes the customer straight to checkout; if False (default) it opens the cart review page.

Returns: JSON with cart_url, the normalised items, item_count, total_quantity, the echoed checkout flag and a short note to show the customer.

Errors (isError=true, body {"error": {...}}): - products_not_found: one or more product_ids do not exist or are not published. The message lists the offending ids. - shop_api_unavailable: the shop could not be reached; retryable.

Notes: - The link SETS the quantities, it does not add to what is already in the cart. Opening the same link twice gives the same result as opening it once, so the customer can safely click it again. - Stock is re-checked when the link is opened. If stock ran out in the meantime, the quantity is reduced or the row skipped — the link can never oversell. - Checkout requires a customer account, so the customer may be asked to log in or register before paying.

ParametersJSON Schema

Name	Required	Description	Default
`items`	Yes	1-20 products to put in the cart
`checkout`	No	If True, the link goes straight to checkout; otherwise (default) to the cart review page

Output Schema

ParametersJSON Schema

Name	Required	Description
`note`	Yes
`items`	Yes
`cart_url`	Yes	Open in a browser to fill the cart
`checkout`	No	True if the link goes straight to checkout, False to cart review
`item_count`	Yes	Number of distinct products
`total_quantity`	Yes	Sum of quantities

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description adds key behaviors: the link sets quantities rather than adds, is idempotent (clicking twice gives same result), stock is re-checked with potential quantity reduction or row skipping, and checkout requires customer account. This goes well beyond the annotation flags and provides rich operational detail.

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?

The description is lengthy but well-structured into Args, Returns, Errors, and Notes sections. Each sentence adds value, though there is slight redundancy with annotations (e.g., 'writes nothing'). It could be tighter, but the organization aids readability.

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 the tool's complexity, the description covers purpose, parameters, return format, error handling, and nuanced behaviors (idempotency, stock re-check, checkout auth). With an output schema and annotations present, the description provides comprehensive guidance for an agent to select and invoke the tool correctly.

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?

Even though schema coverage is 100%, the description adds crucial semantics: repeated product_ids are merged with quantities summed, unknown fields are rejected, explicit ranges for items and quantity, and the effect of the checkout flag. This adds meaning beyond the raw schema and helps the agent construct valid inputs.

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 states 'Build a link that puts the given products into the customer's cart' – a specific verb+resource that clearly distinguishes it from sibling query tools. It also clarifies the tool writes nothing and returns a URL, leaving no ambiguity about its function.

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 clear context: 'Give the URL to the customer and let them click it.' Implicitly distinguishes from sibling tools (which are for querying) but doesn't explicitly state when not to use or name alternatives. The use case is evident, though not exhaustive.

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

get_product_detailsA

Read-onlyIdempotent

Inspect

Get full details and current stock for one Okun Koneosa product.

Args: product_id: The numeric product id returned by search_catalog.

Returns: JSON with the full product record: id, name, name_raw, sku, ean, brand, category, full description (not truncated), price_gross, price_net, vat_percent, currency, unit, weight_kg, product_url, image_url, plus a freshly checked in_stock / stock_quantity.

Notes: - Stock is read at call time from a separate availability endpoint, so it is more current than the value returned by search_catalog. - Returns {"error": "product_not_found"} for unknown or unpublished ids. Products that are out of stock are unpublished, so a previously valid id can stop resolving. - To let the user buy, pass product_url, or build a cart link with create_cart_link.

ParametersJSON Schema

Name	Required	Description	Default
`product_id`	Yes	Product ID from search_catalog

Output Schema

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Product ID — pass to get_product_details or create_cart_link
`ean`	No	EAN/GTIN barcode, when known
`sku`	No	Ordering number used by the shop
`name`	Yes	Readable product name
`unit`	No	Selling unit, e.g. 'kpl'
`brand`	No	Manufacturer
`category`	No
`currency`	No
`in_stock`	Yes
`name_raw`	No	Supplier's own spelling, often ALL CAPS
`image_url`	No	Null for most products — photography is still being collected
`price_net`	Yes	Price excl. VAT
`weight_kg`	No
`disclaimer`	Yes
`description`	No	Full description, not truncated
`price_gross`	Yes	Price incl. Finnish VAT 25.5%
`product_url`	Yes	Public product page
`vat_percent`	No
`stock_checked`	Yes	True if stock was re-read from the availability endpoint
`stock_quantity`	Yes	Units available right now
`description_truncated`	No	True if description was cut — use get_product_details

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context: stock is fetched fresh from a separate endpoint, it returns an error for unknown/unpublished ids, and out-of-stock products become unpublished. No contradiction.

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?

The description is well-structured with clear sections: Args, Returns, Notes. It is concise (every sentence adds value) and front-loaded with the primary purpose. No unnecessary information.

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?

For a simple retrieval tool with 1 param, annotations, and output schema, the description is complete. It covers behavior, error conditions, sourcing of parameters, and relationship to other tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 1 param with description 'Product ID from search_catalog'. The description clarifies it is numeric and from search_catalog, adding meaning beyond the schema. Since schema coverage is 100%, baseline is 3, but the description provides useful sourcing context.

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 'Get full details and current stock for one Okun Koneosa product.' It uses a specific verb ('get') and resource ('product details'), and distinguishes itself from sibling tools like 'search_catalog' (searching) and 'create_cart_link' (building a cart link).

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?

The description explains when to use this tool (to get more current stock than search_catalog) and provides error handling notes. It also mentions that product_id comes from search_catalog, but does not explicitly state when not to use it.

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

search_catalogA

Read-onlyIdempotent

Inspect

Search the Okun Koneosa product catalog.

Okun Koneosa Oy (okunkoneosa.fi) is a Finnish industrial supplies store in Outokumpu, North Karelia. Around 6500 products: bearings, belts, seals, hydraulics, pneumatics, fasteners, hand tools, protective equipment and machine parts. Everything listed is physically in stock. Prices in EUR, including Finnish VAT 25.5%. Free shipping on orders over 150 EUR.

Args: query: Free-text search — matches product name, ordering number (SKU) or EAN code. Leave empty to browse a category. category_id: Restrict to one category. The category list is available at https://okunkoneosa.fi/api/v1/categories (a plain REST endpoint, not an MCP tool). in_stock_only: True by default. The shop only publishes products that are in stock, so this rarely changes the result. sort: "name" (default), "price_asc", "price_desc" or "newest". limit: Products per page, 1-50 (default 10). page: Page number for paging through larger result sets.

Returns: JSON with: - products: list of products, each with id, name, name_raw, sku, ean, brand, category, price_gross (incl. VAT), price_net, currency, unit, in_stock, stock_quantity, weight_kg, product_url, image_url and a shortened description (description_truncated tells if it was cut). - total, page, per_page, total_pages - disclaimer: prices and availability are confirmed at checkout

Notes: - name is cleaned for reading; name_raw is the supplier's own spelling, useful for exact matching against a supplier catalogue. - image_url is null for most products — the shop is still collecting product photography from suppliers. A missing image does not mean the product is unavailable. - Use get_product_details(id) for the full description and a fresh stock check.

ParametersJSON Schema

Name	Required	Description	Default
`page`	No	Page number (>= 1)
`sort`	No		name
`limit`	No	1-50
`query`	No	Free-text search term
`category_id`	No	Category ID
`in_stock_only`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`page`	Yes
`total`	Yes	Total matches across all pages
`per_page`	Yes
`products`	No
`disclaimer`	Yes
`total_pages`	Yes
`suggested_queries`	No	Alternative spellings that DO return results — only present when total is 0

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds behavioral details: stock status, pricing including VAT, free shipping conditions, and notes that image_url is often null. It also mentions that prices are confirmed at checkout.

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?

The description is well-structured with clear sections (Args, Returns, Notes) and front-loaded with the purpose. While slightly verbose, it is organized and each sentence adds value.

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 the 6 parameters and existing output schema, the description is fully comprehensive. It covers the catalog context, parameter details, return structure, and important behavioral notes, leaving no gaps for the agent.

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 description provides detailed explanations for all 6 parameters, including specific options for sort, valid ranges for limit and page, and the behavior of in_stock_only. This adds significant meaning beyond the input schema, which has 67% coverage.

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 'Search the Okun Koneosa product catalog' and provides extensive context about the store and its inventory. It distinguishes itself from sibling tools by explicitly referencing get_product_details for full descriptions.

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?

The description explains when to use the tool (e.g., free-text search, browsing by category) and mentions alternatives like get_product_details for full descriptions. However, it does not explicitly say when not to use it.

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

search_shop_catalogA

Read-onlyIdempotent

Inspect

Search the Okun Koneosa product catalog.

ParametersJSON Schema

Name	Required	Description	Default
`page`	No	Page number (>= 1)
`sort`	No		name
`limit`	No	1-50
`query`	No	Free-text search term
`category_id`	No	Category ID
`in_stock_only`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`page`	Yes
`total`	Yes	Total matches across all pages
`per_page`	Yes
`products`	No
`disclaimer`	Yes
`total_pages`	Yes
`suggested_queries`	No	Alternative spellings that DO return results — only present when total is 0

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavioral detail beyond annotations: in_stock_only rarely changes results, image_url is usually null, prices are confirmed at checkout, and name_raw preserves supplier spelling. No contradiction with readOnlyHint.

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?

Well-organized with Args/Returns/Notes sections; every sentence adds useful information without redundancy.

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 business context (store, stock, VAT, shipping), parameter nuances, output structure, and handles edge cases like missing images. Even provides a pointer to a related tool for more detail.

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?

Description enriches all parameters significantly, e.g., query matching name/SKU/EAN and empty-to-browse, category_id pointing to an external category list, and clear semantics for in_stock_only.

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 clearly states the tool searches the Okun Koneosa product catalog, a specific resource. However, it does not differentiate from the sibling tool 'search_catalog', which may overlap in function.

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 clear context (shop catalog search, browse by category) and explicitly recommends get_product_details for full descriptions and fresh stock checks. Does not address when to prefer search_catalog or other siblings.

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

search_shop_policies_and_faqsA

Read-onlyIdempotent

Inspect

Search Okun Koneosa's shop policies and terms.

Covers delivery terms, privacy policy, terms of service, the consumer right of withdrawal / returns, and company information. Use this instead of guessing when the customer asks about delivery times, shipping costs, returns, warranty or how their data is handled.

Args: query: Finnish keyword, e.g. "palautus", "toimitusaika", "takuu", "toimituskulut". Leave empty to list all sections. limit: Maximum sections to return (1-20, default 5).

Returns: JSON with: - sections: each with page, page_title, heading, content and url - total: how many sections matched - query: the term that was searched

Notes: - Content is split by heading, so you get the relevant paragraph rather than a whole page. Always cite the url so the customer can read the full terms. - These are the shop's own terms. They do not override Finnish consumer law.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Max sections (1-20)
`query`	No	What to look for, e.g. 'palautus', 'toimitusaika'

Output Schema

ParametersJSON Schema

Name	Required	Description
`query`	No
`total`	Yes
`sections`	No

TDQS

A5/5.0

Behavior5/5

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

Discloses that content is split by heading to return relevant paragraphs, advises to cite url, and notes that shop terms do not override Finnish law. Annotations are consistent and description adds value beyond them.

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?

Well-structured with Args, Returns, and Notes sections. Front-loaded with purpose. Every sentence adds necessary information without redundancy.

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 2 simple parameters, an output schema described in Returns, and annotations, the description provides all needed context including behavior, limitations, and guidance. No gaps.

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?

Input schema covers both parameters with descriptions, and the description adds concrete examples (e.g., 'palautus', 'toimitusaika') and explains behavior when query is empty. Schema coverage is 100% but description enriches usage.

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?

Clearly states the tool searches Okun Koneosa's shop policies and FAQs. Lists specific topics (delivery, privacy, returns, etc.) and distinguishes from sibling tools like search_catalog which handles products.

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?

Explicitly says 'Use this instead of guessing when the customer asks about delivery times, shipping costs, returns, warranty or how their data is handled.' Provides concrete usage context and alternatives.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateAug 5, 2026
- Addedsearch_shop_catalog

1 tool updateAug 5, 2026

Changedcreate_cart_link2 fields changed

addedInput schema / properties / checkout

Added value: +{
+  "default": false,
+  "description": "If True, the link goes straight to checkout; otherwise (default) to the cart review page",
+  "type": "boolean"
+}

addedOutput schema / properties / checkout

Added value: +{
+  "default": false,
+  "description": "True if the link goes straight to checkout, False to cart review",
+  "title": "Checkout",
+  "type": "boolean"
+}

4 tool updatesJul 28, 2026
- First observedcreate_cart_link
- First observedget_product_details
- First observedsearch_catalog
- First observedsearch_shop_policies_and_faqs

Related MCP Connectors

rakentaja-outlet A
fi.rakentajaoutlet
Finnish e-commerce for electrical & construction supplies. Read-only MCP with 4 tools.
E-commerce & Retail Search
52
store A
com.bolotstudio
Custom metal-print storefront: catalog search, product details, shipping, reviews. Read-only.
E-commerce & Retail Search
112
HPControl Industrial Catalog A
pl.hpcontrol
B2B industrial valves, solenoid valves & pneumatic actuators. Search & build a cart.
E-commerce & Retail Search
82
Hilma A
io.github.pipeworx-io
Hilma MCP — Finnish government public procurement notices (keyed).
Government Data Open Data
342

Related MCP Servers

finnish-foreign-trade-mcp
Government Data Open Data Research & Data
NectiaAutomation
A
license
Not graded
quality
C
maintenance
https://github.com/NectiaAutomation/finnish-trade-mcp-server
Updated 2 months ago (2026-07-19 09:44 UTC)
4 npm
MIT
k-ruoka-mcp
E-commerce & Retail Browser Automation
nikosavola
A
license
Not graded
quality
A
maintenance
MCP server that manages a K-Ruoka (Finnish grocery) shopping cart: read cart, add/update/remove items, clear cart, search products and stores. It uses a real Chrome browser to authenticate via cookies, enabling cart management through natural language.
Updated a month ago (2026-08-13 17:24 UTC)
1
Apache 2.0
hilma-mcp-server
Government Data Search
NectiaAutomation
A
license
Not graded
quality
C
maintenance
MCP server for Finnish public procurement (HILMA): search tenders, awards and procurement plans by keyword, CPV, region and buyer, and fetch full notice details.
Updated 2 months ago (2026-07-19 07:00 UTC)
4 npm
MIT
nordic-registry-mcp-server
Government Data Open Data Search
olgasafonova
A
license
Not graded
quality
A
maintenance
MCP server for Nordic company registries. Verify companies, check board members, signing authority, and financial data across Norway, Denmark, Finland, and Sweden using official public APIs. 23 tools covering search, details, roles, and batch lookups.
Updated 3 days ago (2026-09-14 20:34 UTC)
19
8
Apache 2.0

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?