Skip to main content
Glama

Campo Belo

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

A5/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. It explains the effect of the parameter and what the tool returns (plan details and checkout URL), giving full 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?

Three sentences with no extraneous information: purpose, parameter guidance, return fields. Well-structured and efficient.

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 one optional parameter and no output schema, the description covers all necessary information: what it does, how to use it, and what it returns. Completely adequate.

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

Parameters5/5

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

The schema covers the parameter with 100% coverage, and the description adds extra context about its significance and when to use it, reinforcing the schema's guidance.

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 'List membership or subscription plans (Wix Pricing Plans)', specifying the verb and resource. It distinguishes from sibling tools by explaining the two use cases (venue-specific vs directory-wide plans).

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 when to pass `place_slug` (for venue plans, 'almost every case') and what happens when omitted (directory's own plans). It provides clear guidance on the typical use case.

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

All Campo Belo 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.1/5.0
Disambiguation5/5

Each tool targets a distinct action on a specific resource (e.g., create_booking vs create_checkout vs reserve_event_tickets). Descriptions clearly differentiate purposes, and no two tools overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_availability, list_categories, search_dishes). Verbs like get, list, create, request, rsvp are used uniformly, making the set predictable.

Tool Count4/5

28 tools is above the typical 3-15 range, but the server covers a broad domain (places, events, movies, booking, store, etc.). Each tool serves a clear purpose, so the count is justified for the scope.

Completeness4/5

The tool surface is extensive, covering searching, details, reviews, booking, events, menus, etc. Minor gaps exist (e.g., no cancel/update operations), but they are likely intentional given the user-facing nature of the server.

Resources