Najdi nářadí nebo příslušenství podle názvu, kódu, EANu nebo potřeby (např. "váleček", "špachtle", "maskovací páska", "brusný papír"). Vrací název, cenu s DPH, skladovost a odkaz.
| Name | Required | Description | Default |
|---|---|---|---|
| dotaz | Yes | Co hledáš — název, kód, EAN nebo popis potřeby. | |
| limit | No | Kolik výsledků (1–30, výchozí 10). | |
| jen_skladem | No | true = vrátit jen to, co je fyzicky skladem. Výchozí false. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the transparency burden and does a good job by stating what the tool returns: name, price incl. VAT, stock availability, and a link. It implicitly communicates a read-only search operation, though it does not cover edge cases such as no results or ordering behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: it states the action, gives representative examples, and then lists the return fields in one additional sentence. Every part earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a relatively simple search tool, the description plus fully covered schema gives an agent enough to invoke it correctly. It states the return payload, parameter semantics are documented, and no output schema exists to explain further. A minor gap is the lack of explicit failure/no-result behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents all three parameters with 100% coverage, so the baseline is 3. The description adds value by giving real example values for 'dotaz' such as 'váleček', 'špachtle', and 'maskovací páska', which helps the agent form valid queries.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Najdi nářadí nebo příslušenství') and lists search keys (name, code, EAN, need) with concrete examples. It is easy to understand what the tool does, but it does not explicitly differentiate it from sibling catalog or assortment tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended use is implied clearly: search for products by various identifiers or needs. However, there is no explicit guidance about when to prefer this tool over painto_sortiment, painto_katalog_pdx, or painto_dostupnost, and no exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a different customer need: search, availability, shipping/payment, catalog ordering, contact, and assortment stats. The only mild overlap is between painto_hledej and painto_dostupnost, since both surface stock information, but their intended use cases are distinct enough.
All tools share the painto_ prefix and lowercase snake_case style, making them easy to recognize as a group. The set is mostly noun-style with one imperative exception (painto_hledej), so it is predictable but not a uniform verb_noun pattern.
Six tools is a well-scoped size for an e-shop assistant. Each tool clearly earns its place and covers a meaningful slice of customer-facing functionality without redundancy or unnecessary bloat.
The tool set covers the core shopping-help workflows: finding products, checking stock, getting shipping and payment details, contacting the store, and ordering via catalog. Minor gaps such as detailed product pages, promotion listings, or order status exist, but agents can usually work around them.