Skip to main content
Glama

Olé Futebol

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.7/5.0
Behavior4/5

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

No annotations are provided, so description carries full burden. It discloses the return fields (name, description, price, billing cycle, perks, checkout URL). However, it does not explicitly state that the operation is read-only or safe, nor does it mention authentication requirements. While agents can infer safety, explicit disclosure would improve transparency.

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?

The description is a single paragraph, front-loaded with the main purpose, then explains the parameter and finally lists return fields. Every sentence adds value with no redundant information. Very concise and well-structured.

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?

Given the tool has only one optional parameter, no output schema, and 26 sibling tools, the description fully covers the needed context: two usage scenarios, parameter guidance, and return value fields. It is complete enough for an agent to select and use the tool correctly.

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%, baseline 3. The description adds context beyond schema: it explains why `place_slug` is strongly recommended and what happens when omitted (directory's own plans vs venue plans). This added semantics justifies a score of 4.

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 clearly states it lists membership/subscription plans from Wix Pricing Plans. It specifies the verb 'List' and the resource 'pricing plans', and distinguishes between two use cases: with a venue slug (venue-specific) and without (site-wide plans). This fully clarifies the tool's purpose.

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

Usage Guidelines5/5

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

The description explicitly tells the agent to pass `place_slug` from `search_places` for venue-specific plans, stating that is the desired case 'in almost every case'. It also warns that omitting it gives directory site's own plans, which most sites do not have. This provides clear when-to-use guidance and differentiates from potential alternatives.

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

All Olé Futebol 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 resource or action (booking, checkout, availability, events, reviews, etc.). Even similar-looking tools like create_booking, request_reservation, and rsvp_event are clearly differentiated by their descriptions and target systems.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_booking_services). No mixing of conventions or unclear verbs.

Tool Count4/5

28 tools is on the higher end, but the server covers a wide domain (places, events, movies, booking, forms, loyalty, etc.). Each tool serves a clear purpose, so the count is justifiable, though minor trimming could be considered.

Completeness4/5

The tool set covers most workflows for a neighborhood directory: search, details, booking, events, reviews, etc. Some CRUD operations are missing (no update/delete for bookings), but these are consumer-facing actions where that is acceptable. The domain is well-covered.

Resources