Listázza az aktuálisan RAKTÁRON lévő szabvány nyílászárókat és kiegészítőket valós idejű bruttó árral és készlettel. Lists current ready-stock items with retail prices and inventory.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must fully convey behavior. Mentions 'real-time' but no detail on data freshness, auth requirements, or side effects. Minimal disclosure.
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?
Two brief sentences per language, front-loaded with key info. No superfluous text, though bilingual duplication slightly reduces conciseness.
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?
Adequate for a parameterless tool, but lacks output schema or description of return format/pagination. Minimal for full contextual completeness.
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?
No parameters exist, so baseline 4. Description doesn't need to add parameter info, and schema coverage is 100% (trivially).
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?
Clearly states the tool lists currently in-stock standard doors/windows and accessories with real-time gross price and inventory. Differentiates from sibling tools (quote-related) by focusing on inventory retrieval.
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?
Implies usage when real-time stock info is needed ('current ready-stock items'), but no explicit when-to-use, when-not-to-use, or alternatives given.
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 distinct action: requesting a two-step quote, confirming it, getting a price estimate, and listing inventory. No overlap or confusion.
All tool names follow a consistent verb_noun pattern using snake_case: request_quote, confirm_quote, get_price_estimate, list_inventory.
Four tools is well-scoped for a window and door ordering server, covering the essential customer-facing actions without excess.
Covers core workflows (price inquiry, stock check, quote request with confirmation). Missing a tool to view or manage existing quotes, but the surface is functional for initial use.