Compute the effective bulk price for a given product and quantity: applies the product's quantity-discount tiers and GST, validates the minimum order quantity, and shows the next discount tier. Indicative pricing — final quotes come from the sales team.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Product permalink slug or id (from search-products) | |
| quantity | Yes | Number of units |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does so well. It discloses the computation steps (quantity-discount tiers, GST), validation of minimum order quantity, that the next discount tier is shown, and the limitations of indicative pricing. This gives the agent a solid model of what the tool does and doesn't do.
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 sentences, front-loaded with the primary action, and every clause adds information: computation method, validation, next-tier output, and a caveat. No filler or redundancy.
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?
Despite having no output schema, the description adequately communicates what the tool returns: effective price, next discount tier, and validation status. It covers the main behavioral aspects (tiers, GST, MOQ, indicative pricing) and is sufficient for an agent to select and invoke the tool correctly.
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?
Since schema description coverage is 100% and both parameters are well-described, a baseline of 3 is appropriate. The description adds some context by mentioning quantity-discount tiers and MOQ validation, which slightly enriches the 'quantity' parameter, but it doesn't add substantial parameter-level details beyond the schema.
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 opens with a specific verb ('Compute') and resource ('effective bulk price') and clearly identifies the inputs (product and quantity). It distinguishes itself from siblings like search-products and request-quote by focusing on pricing calculation rather than product discovery or final quoting.
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 implies when to use the tool (to get an indicative bulk price) and explicitly warns that final quotes come from the sales team, effectively steering users away from using this for binding quotes. It doesn't explicitly name alternatives, but the context of siblings like request-quote makes the distinction clear.
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 or resource: product discovery vs pricing vs orders vs meetings vs support. While get-company-info, get-site-info, and get-guide all provide reference material, their scopes are clearly separated (verified facts vs FAQ/how-it-works vs published articles). No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern in snake_case: book-, cancel-, reschedule-, get-, search-, list-, request-, track-, reorder-, create-. Even exceptions like my-orders and my-invoices fit a possessive pattern that is predictable. No mixed conventions or vague verbs.
24 tools is on the high end but appropriate for the breadth of this server's scope: product catalog, pricing, meetings, orders, invoices, support, guides, company info, and SEO. Each tool fills a specific niche, and none feel redundant. It is slightly heavy but not overwhelming for the domain.
The tool surface covers the core workflows well: product search/details/pricing, meeting booking/cancel/reschedule, order viewing/tracking/reordering, quotes, complaints, callbacks, invoices, guides, and company information. A minor gap is the absence of a direct 'place new order' tool, but request-quote and reorder handle the necessary paths, and other interactions (e.g., complains) have clear entry points.
