okun-koneosa

search_catalog

Read-onlyIdempotent

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.

Input Schema

TableJSON 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

TableJSON 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.

All okun-koneosa tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

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.

Resources

Need Help?