Skip to main content
Glama

Bom Retiro

by io.github.junoventures

list_pricing_plans

List membership or subscription plans (Wix Pricing Plans). Pass place_slug (from search_places) to list the plans of a specific VENUE — a gym, studio or clinic listed in this directory (e.g. its monthly/annual membership); that is what you want in almost every case. Omitting place_slug lists the directory site's own plans instead, which most sites do not have. Returns plan name, description, price, billing cycle, perks, and a direct checkout URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
place_slugNoVenue place slug from search_places. Strongly recommended — without it you get the directory's own plans, not a venue's.

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries full burden. It discloses behavior variation based on parameter presence and lists return fields (name, description, price, billing cycle, perks, checkout URL). No destructive actions or auth needs mentioned, but appropriate for a read-only list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with clear structure: purpose first, then detailed guidance. No superfluous words; every sentence provides essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully covers return values and explains both usage scenarios. For a simple 1-parameter tool, it is complete and self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (place_slug described). The description adds value by explaining where to get the slug (search_places) and the consequence of omitting it, going beyond the schema's description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'List membership or subscription plans' and differentiates between the two use cases (with and without place_slug), clearly distinguishing the tool from siblings like list_booking_services or list_products.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance: 'Pass place_slug... that is what you want in almost every case' and explains the alternative (omitting it lists directory's own plans). It references search_places as a prerequisite but does not explicitly exclude alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bom Retiro toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct domain (bookings, store, events, restaurants, movies, etc.) with detailed descriptions that clearly differentiate their purposes. Overlap is minimal and handled by context, such as create_booking vs create_checkout vs request_reservation.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case, using prefixes like get_, list_, create_, search_, etc. The naming is predictable and makes it easy to infer the action and resource.

Tool Count4/5

28 tools is above the typical well-scoped range, but each tool covers a distinct feature of the neighborhood directory (places, events, movies, blog, forms, etc.). The count reflects the integration of multiple Wix apps, which is appropriate for a comprehensive directory.

Completeness4/5

The tool set covers most user-facing operations for a directory: search places, get details, book services, events, restaurant menus, etc. Minor gaps exist (e.g., no cancellation for bookings, no update operations), but these are likely out of scope for a public-facing server.

Resources