Get full details for a specific place by its URL slug, including opening hours, a precomputed open_now boolean, amenity attributes (slugs), a delivery array of curated delivery-app deep-links (ifood, rappi, uber-eats — each { platform, url }), ratings, address, and neighborhood.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | URL slug of the place, e.g. "cafe-example". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It lists returned fields but does not disclose behavioral traits such as error handling, rate limits, authorization requirements, or what happens with invalid slugs.
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 two sentences with no wasted words. It front-loads the purpose and then lists key return fields. Structure is clear and efficient.
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?
Given the single parameter and no output schema, the description compensates by enumerating return fields (opening hours, open_now, attributes, delivery, etc.). It lacks edge-case or error information but is otherwise thorough for a simple get-detail 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 description coverage is 100% for the single parameter 'slug'. The description adds 'by its URL slug' which is consistent with the schema's 'URL slug of the place', but does not provide significant additional meaning 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 clearly states the verb 'Get', the resource 'full details for a specific place', and the mechanism 'by its URL slug'. It lists specific data fields returned, distinguishing it from sibling tools like search_places.
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 usage for fetching details of a single place but does not explicitly state when to use this versus alternatives like search_places. No when-not or alternative tool guidance is provided.
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.
Every tool targets a distinct Wix resource or action: bookings, events, store, forms, places, menus, etc. The four booking-related tools are clearly separated by domain (appointments, restaurant tables, paid events, free events), with descriptions that eliminate ambiguity.
The set follows a consistent verb_noun snake_case pattern (create_, get_, list_, search_, submit_). Minor deviations exist: get_reviews and get_event_tickets return collections (could be list_), and rsvp_event uses an abbreviation, but these do not affect clarity.
At 26 tools, the set is larger than the typical 3–15 well-scoped range, but the server covers a broad umbrella of Wix integrations for a neighborhood directory. Each tool maps to a distinct function, so the count is justified by the scope, though it is on the heavier side.
The surface covers discovery and transactional workflows: searching places/dishes, viewing menus/reviews/guides/offers, booking appointments and tables, reserving event tickets, purchasing products, submitting forms, and reading site info. Minor gaps exist (no cancel/update operations), but these are handled via external checkout links and are acceptable for a directory.
