PDX — interaktivní katalog Painto. Zákazník si ve stránkách katalogu odfajfkuje zboží a pošle to jako objednávku nebo poptávku, i bez zakládání účtu. Použij, když se někdo ptá na katalog, ceník, nebo chce objednat víc položek najednou.
| 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?
With no annotations provided, the description carries the full transparency burden. It usefully discloses that the customer can act without creating an account and that the interaction results in an order or inquiry being sent. It does not describe what happens after submission or the exact return behavior, but the added behavioral context is meaningful.
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 only two sentences. The first frames what the tool is and how it behaves, and the second gives the invocation triggers. Every clause adds value, with no filler or redundant schema repetition.
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 catalog tool, the description covers the purpose, user flow, account requirement, and when to use it. The only minor gap is that it does not explicitly state what the agent should return or display to the user, but that is not critical given the interactive nature of the catalog.
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 and the schema is already 100% covered by the empty properties object. The description appropriately adds no parameter details. Per the baseline for no-parameter tools, this is a 4.
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 names a specific resource (interactive Painto catalog) and explains the core action: customers check off goods and send them as an order or inquiry. It also distinguishes itself from siblings by calling out catalog, price list, and multi-item ordering use cases, which sets it apart from search, availability, and contact 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 description gives an explicit trigger condition: 'Use when someone asks for a catalog, price list, or wants to order multiple items at once.' This is clear context for when to invoke the tool. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.
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.