Skip to main content
Glama

Jardins

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, but description fully explains read-only listing behavior, return fields, and two operational paths. Lacks mention of authentication or pagination, but not required for a simple list.

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: first states purpose and key instruction, second explains alternative. Every word earns its place, front-loaded, no redundancy.

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?

Simple tool with one optional parameter and no output schema; description covers resource, behavior, parameter guidance, and return fields. Complete for agent decision-making.

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?

Schema covers parameter 100%, but description adds crucial context: strongly recommended, purpose, and source (search_places). Significantly enriches meaning.

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?

Description clearly states 'List membership or subscription plans' with specific resource and distinguishes between two modes (with and without place_slug). Returns explicit fields. No confusion with siblings.

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 instructs to pass place_slug from search_places to get venue plans, and warns that omitting it yields directory's own plans (rare). Provides clear when-to-use and alternatives.

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

All Jardins 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.2/5.0
Disambiguation5/5

Each tool targets a distinct action and resource, such as booking, checking availability, listing events, or searching dishes. No two tools appear to overlap in purpose, and descriptions clearly differentiate them.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., create_booking, get_availability, list_events, search_places). The prefixes (create, get, list, search, request, reserve, rsvp, submit) are uniformly applied, and there is no mixing of cases or styles.

Tool Count4/5

With 28 tools, the server covers a broad feature set for a neighborhood directory, including bookings, store, events, loyalty, menus, movies, and more. While slightly high, each tool serves a distinct purpose and is justifiable.

Completeness5/5

The tool surface appears complete for the domain: search, details, booking flows, store purchases, events, loyalty, reviews, blog, offers, profiles, forms, and FAQ are all covered. There are no obvious dead ends, and operations for CRUD or lifecycle are present where needed.

Resources