Skip to main content
Glama

Gracie Barra Jiu-Jitsu

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

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

No annotations provided, but the description clearly indicates it's a read operation (lists plans) and details the return fields (name, description, price, billing cycle, perks, checkout URL). Lacks mention of authentication or rate limits, but those are reasonable omissions for a listing 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?

Concise single paragraph. First sentence states purpose, then parameter guidance, then return fields. No unnecessary words, front-loaded, every sentence serves a purpose.

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?

For a simple listing tool with one optional parameter, the description fully covers what the tool does, when to use it, and what it returns. No output schema is provided, but the description lists return fields, compensating adequately.

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 one parameter, place_slug, is well-described in both schema and description. The description adds context: strongly recommended, explains the consequence of omission, and mentions its source. Adds significant value 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 specifically states it lists membership or subscription plans (Wix Pricing Plans), distinguishes between listing for a specific venue vs the directory's own plans, and differentiates from sibling tools which are not about pricing 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?

Explicitly says when to use place_slug (for venue plans, which is almost always) and when not to (directory's own plans, rare). Provides source for place_slug (search_places). No ambiguity.

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

All Gracie Barra Jiu-Jitsu 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 and action. Even similar operations like create_booking, request_reservation, reserve_event_tickets, and rsvp_event are clearly differentiated by their descriptions and the entities they handle (bookable services, restaurant tables, paid events, free events). No two tools appear to do the same thing.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., create_booking, get_availability, list_events, search_places). This uniform convention makes the tool set predictable and easy for an agent to understand and select from.

Tool Count3/5

With 28 tools, the set is relatively large, exceeding the typical well-scoped range of 3-15. While each tool serves a specific purpose within the neighborhood directory domain, the count feels heavy and may overwhelm simple use cases. A reduction or grouping could improve coherence.

Completeness4/5

The tool set covers a broad range of user-facing operations for a neighborhood directory: searching places, browsing menus, booking services, reserving tables and event tickets, listing products and events, retrieving reviews and FAQs, and submitting forms. Minor gaps exist (e.g., no cancellation or create_review tool), but the core workflows are well-supported.

Resources