Přehled sortimentu e-shopu Painto.cz (malířské a stavební nářadí) — kolik produktů je v nabídce a kolik z nich skladem. Začni tímhle, ať víš, co obchod nabízí.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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?
No annotations are provided, so the description must carry the behavioral disclosure. It discloses that the tool reports counts of products and stock availability, which is useful. However, it does not explicitly state that the operation is read-only, nor describe response format, latency, or any side effects. For a simple overview tool this is adequate but not richly transparent.
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 a single well-structured sentence that front-loads the main purpose, includes the specific metrics, and ends with a clear usage recommendation. No filler or redundant content.
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 zero-parameter tool with no output schema, the description fully explains what the tool does, what information it provides, and when to use it. The sibling tools are not needed to disambiguate because this tool's role as an assortment overview is self-contained. Nothing essential is missing.
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 tool has zero parameters, so parameter-level documentation is unnecessary. The schema confirms an empty parameter object, and the description adds the relevant context of what the output will summarize. The baseline of 4 for zero-parameter tools applies.
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 tool provides an overview of the e-shop assortment with two specific metrics: total products and in-stock products. It names the resource (Painto.cz assortment) and the scope (painting and construction tools), making the purpose understandable. It does not explicitly contrast with siblings, but the purpose is specific enough to stand on its own.
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 description includes an explicit usage cue: 'Začni tímhle' (start with this) to learn what the shop offers. This gives clear context for when to call the tool. It does not mention when not to use it or name alternatives, but for a zero-parameter overview tool this is reasonably complete guidance.
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.