Skip to main content
Glama

Tatuapé

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

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

With no annotations, description covers return fields (name, price, etc.) and behavior regarding place_slug, but does not explicitly state read-only nature or potential side effects.

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 concise sentences with no wasted words, front-loading purpose then providing essential guidance.

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

Completeness4/5

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

Given no output schema and one optional parameter, description covers key return fields, parameter usage, and typical scenarios; minor gap on pagination or limits, but overall complete enough.

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?

Input schema already covers the parameter with description; the tool description adds value by explaining the contextual difference between providing and omitting place_slug, which is beyond the schema.

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 the tool lists membership or subscription plans, distinguishes between venue-specific and directory plans, and differentiates from sibling tools like list_products or list_booking_services.

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?

Explicitly recommends using place_slug in almost every case, explains consequence of omitting it, and clarifies typical use case for venue plans.

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

All Tatuapé 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 has a clearly distinct purpose, even among similar actions like booking, reservation, and ticket purchase—their descriptions clarify the domain and flow. No two tools could reasonably be confused.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_blog_posts). There are no deviations or mixed conventions.

Tool Count3/5

At 28 tools, the surface is larger than ideal for a single server, but each tool covers a distinct feature of the neighborhood directory (bookings, events, store, etc.). It borders on heavy but is still manageable for an agent.

Completeness5/5

The tool set covers the full lifecycle of browsing and acting on a neighborhood directory: search, details, reviews, menus, events, booking, reservations, store, loyalty, and more. No obvious gaps exist for the intended use case.

Resources