List active promotions and deals available in this neighborhood directory. Returns discount label, promo code (if any), CTA link, validity window, and which business/place it belongs to. FLASH offers have a countdown deadline.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Filter by offer kind. FLASH = time-limited flash sale with countdown. Omit to return all active offers. | |
| limit | No | Max offers to return (default 20, max 60). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavior. It mentions return fields and FLASH countdown but lacks side-effect info, auth needs, or read-only guarantee. Adequate but not thorough.
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?
Three concise sentences with front-loaded purpose. No wasted words, clear structure.
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?
Explains return fields and FLASH distinction. Lacks pagination details (e.g., offset, default ordering) and whether the list is exhaustive. Good but incomplete for a list tool.
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?
Schema covers both parameters 100%, baseline 3. Description adds context about FLASH offers relating to kind enum but does not enrich limit parameters beyond schema. Minimal added value.
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?
Description clearly states the tool lists active promotions/deals in a neighborhood directory, specifies return fields (discount label, promo code, etc.), and distinguishes FLASH offers. Differentiates well from sibling list tools for other entities.
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?
Description implies the tool is for promotions but does not provide explicit guidance on when to use it vs. siblings (e.g., list_events, list_products). No when-not-to-use or alternative cues.
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 domain (booking, store checkout, events, restaurant, etc.) with clear descriptions. No two tools have overlapping purposes; even similar actions like create_booking, create_checkout, and reserve_event_tickets are differentiated by their specific contexts.
All tools follow a consistent verb_noun pattern with underscores (e.g., get_availability, list_blog_posts, reserve_event_tickets). There is no mixing of conventions like camelCase, and verbs are predictable (get, list, create, search, submit, etc.).
With 28 tools, the count is slightly on the high side but justified by the broad scope covering a neighborhood directory with multiple features (places, events, movies, menus, bookings, forms, etc.). Each tool serves a clear purpose, though a few could be consolidated.
The tool surface is comprehensive for the server's purpose, covering search, details, bookings, events, movies, menus, blogs, FAQs, forms, and more. Minor gaps exist (e.g., no tool to cancel bookings or update reviews), but core workflows are well-covered.