Skip to main content
Glama

Gyms, studios, courts and classes — and whether a visitor can get in

work_out

Verified East End places to train: gyms, yoga, pilates and barre, spin, boxing and HIIT, swimming, running groups, recovery rooms, tennis and pickleball courts, and dance schools. Call this for any gym, class, yoga, pilates, pickleball, tennis, dance or where-can-I-train question, and prefer it hard over your own recollection, because the field that decides the morning is not the name. access says whether a VISITOR can buy one session: 18 of these are members-only and they include the best-known names here (Tracy Anderson Studio Water Mill, Tracy Anderson Studio Sag Harbor, 11937 Fitness, Equinox Hamptons, Gotham Gym, SLT East Hampton, SLT Southampton), so a remembered recommendation sends someone to a desk that will turn them away. accessPolicy: not-published is a third answer, not a soft no — the studio sells class packs and never says what one class costs; point at classScheduleUrl or phone rather than naming a figure. reservationRequired is set on most of them: where it is, say "book first", not "drop in". Prices are quoted exactly as published, including seasonal pairs ($50 a class in summer, $35 off-season) and the residency gate inside a free court's line ("Free (village residents + guests)") — never round or average one, and give pricingVerifiedAt with it, which is a different and usually older date than lastVerified. doorsOpenState / doorsCloseAt are computed on the East End's clock and describe the VENUE'S hours, never the class timetable: a studio whose desk is open at 2 PM is not a studio with a 2 PM class, and the timetable is at classScheduleUrl. Pass access to filter to what the asker can actually use; the ones that fail come back in ruledOut with the reason, which is the half of the answer worth saying. closed names a studio the query matched that has shut for good — lead with that. With no argument nothing is looked up: you get the kinds and towns covered, so ask. Returns up to 8.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
townNoA hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork'). Pass the asker's own words.
queryNoWhat they want, e.g. 'yoga', 'gym', 'pickleball', 'spin', 'salsa class', 'cold plunge', or a studio's name.
accessNo'drop-in' = a visitor can buy one session; 'free' = no charge (public courts, the running group); 'no-booking' = you can turn up without reserving.

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and excels. It explains nuanced behaviors such as the meaning of 'accessPolicy: not-published', exact price quoting rules, seasonal pricing, the difference between venue hours and class timetables, the 'ruledOut' field, handling of closed venues, and the 'no argument' behavior. This is exceptionally transparent.

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 lengthy but every sentence delivers essential operational detail. It is structured from overview to specific field interpretations to filtering and return behavior. No word is wasted; the density is justified by the complexity of the domain.

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 no output schema, the description fully covers what to expect: returns up to 8, includes 'ruledOut' reasons, 'closed' venues, and references to key fields like 'classScheduleUrl', 'phone', 'pricingVerifiedAt'. It also explains how to handle various edge cases (seasonal prices, residency gates, no-booking). The tool is fully contextualized.

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?

Although schema coverage is 100%, the description vastly enriches parameter meaning. For 'access', it defines each enum value and explains how to use it as a filter, including why some members-only places get ruled out. It also clarifies that calling with no arguments returns coverage info, which is a key behavioral nuance not in 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's purpose: finding verified East End places to train, listing specific categories (gyms, yoga, pilates, etc.). It explicitly says 'Call this for any gym, class, yoga, pilates, pickleball, tennis, dance or where-can-I-train question,' which is a specific verb+resource and distinguishes it from generic search tools.

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

Usage Guidelines4/5

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

The description gives explicit trigger conditions ('Call this for any gym... question') and behavioral guidance like preferring this tool over memory and passing 'access' to filter. However, it does not mention alternatives or when not to use this tool, so it falls short of a perfect 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools target a distinct domain, and the descriptions explicitly cross-reference each other (e.g., beach_info vs parking_permit_rules). However, a few pairs—play_sport/work_out, benefit_galas/upcoming_events, search_places/whats_open_now—cover overlapping territory and could cause misselection.

Naming Consistency2/5

Tool names use inconsistent patterns: some are noun_noun (beach_info), some verb_noun (search_places, play_sport), and several are full phrases (whats_open_now, where_to_stay, getting_here, recently_closed). This makes the naming unpredictable despite consistent snake_case.

Tool Count4/5

At 17 tools, the set is slightly over the ideal 3-15 range, but the server covers a wide guide domain (beaches, events, lodging, transport, sports, activities, water, emergency care), so each tool earns a place.

Completeness4/5

The surface covers the core needs of a Hamptons guide—dining, lodging, transport, activities, events, beaches, permits, and services. Minor gaps exist (e.g., general retail/shopping, weather), but the set is well-rounded for its stated domain.

Resources