Skip to main content
Glama
Sign In

nyc-tennis-courts

by tennis.courts
OverviewDiscussionsAdmin

Server Details

Where to play tennis in New York, London, Paris and more cities: walk on, book or join. Sourced.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 79 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation4/5

find_courts (multi-city venue search) and get_court (single venue detail) are cleanly separated by taking a slug, and list_cities is a distinct city-level discovery tool. The main blur is between list_cities and how_to_play_tennis_in_nyc, which both summarize how you get on a court, and both carry long 'start here' imperatives that could confuse an agent about which to call first.

Naming Consistency3/5

Three tools follow a readable verb_noun snake_case pattern (find_courts, get_court, list_cities), but how_to_play_tennis_in_nyc breaks the convention with a full sentence-style name. There is also a minor singular/plural mismatch between find_courts and get_court.

Tool Count4/5

Four tools for a read-only court directory is lean but each has a distinct job: search, detail lookup, city index, and city-specific guidance. It sits at the thin end of reasonable rather than being over-scoped.

Completeness4/5

Search plus detail lookup covers the full read-only lifecycle of a directory, and the explicitly acknowledged absence of a floodlights filter is handled honestly. The asymmetry of a dedicated how_to_play tool for New York City only, with no equivalent guidance for the other 47 cities, is the notable gap.

Available Tools

4 tools
find_courtsFind places to play tennis in one cityA
Read-onlyIdempotent
Inspect

Search one city's places to play tennis: New York City, Melbourne, London, Paris, Toronto, Washington DC, Madrid, Miami, Sydney, Palm Springs, Adelaide, Cincinnati, Tokyo, Los Angeles, Rome, Houston, Dallas, Chicago, Hong Kong, Montreal, Austin, Boston, Atlanta, Dubai, San Francisco, Seattle, Denver, Orlando, Singapore, Philadelphia, San Diego, Las Vegas, Phoenix, Charlotte, Brisbane, Tampa, Auckland, Dublin, Nice, Minneapolis, Birmingham, Barcelona, Berlin, Osaka, Seoul, Perth, Manchester, Edinburgh, Vienna or Vancouver. Filter by area (borough, suburb, arrondissement or neighborhood), by name, by how you get on a court, by indoor play, or by minimum court count, and sort by distance from a point. Returns each venue with its page URL. There is no floodlights filter: the records are too sparse to filter on without hiding real lit courts.

NameRequiredDescriptionDefault
areaNoBorough (New York, London), suburb (Melbourne, Sydney), arrondissement (Paris) or the neighborhood the city itself puts the venue in (Toronto, Atlanta, Washington DC), exactly as the directory names it, e.g. Manhattan, Camden, Kooyong, Islington, Old Fourth Ward, "Capitol Hill, Lincoln Park". A name that matches nothing returns the city's valid areas.
cityNoWhich city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, nice, minneapolis, birmingham, barcelona, berlin, osaka, seoul, perth, manchester, edinburgh, vienna, vancouver (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for.
nameNoPart of a venue's name, e.g. "central park". Case and accents are ignored.
limitNoMaximum venues to return. Default 25, maximum 150.
accessNoHow you get on a court. New York: walk_on (public park, no booking), reservation (public park court bookable through NYC Parks), private_club (runs its own booking). Every other city: walk_on, book (open to the public by booking), members_only, mixed (more than one arrangement at the venue: read its accessDetail), public (the source lists public courts and states no walk-on or booking rule; where its own page says more, that is the venue's accessDetail or price, in the source's words). A value a city does not use is refused with the ones it does.
boroughNoSame as area. Kept for callers written when the directory was New York only.
minCourtsNoMinimum number of courts at the venue. Venues whose court count is not sourced are left out when this is set.
indoorOnlyNoOnly venues where a source confirms indoor or covered courts, which may be some courts, or winter only: read indoorOrCovered on each. Venues never researched are excluded rather than assumed outdoor.
nearLatitudeNoWith nearLongitude: sort by distance from this point, nearest first.
nearLongitudeNoWith nearLatitude: sort by distance from this point, nearest first.

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is credited for what it adds: that each venue is returned with its page URL, and the deliberate data-driven omission of a floodlights filter. The refusal behaviors for invalid access values and empty area matches add useful operational context, though there is no note on pagination or result volume beyond the limit parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the floodlights caveat are front-loaded and valuable, but roughly half the description is a ~50-city enumeration that duplicates the city enum verbatim and burns a large amount of space for no new information. The filter sentence and the closing caveat earn their place; the city list does not.

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?

For a 10-parameter, all-optional search tool with no output schema, the description covers the searchable dimensions, states that results include venue page URLs, and flags the one surprising absence (no floodlights filter). Remaining gaps are minor, e.g. no explicit statement of how sorting interacts with filtering or of result ordering when no distance point is supplied.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline of 3 applies: the description's mention of area/name/access/indoor/min-courts/distance sort simply mirrors what the schema already documents in richer detail. It adds no new semantics such as default values or enum nuances beyond what is already in the field descriptions.

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 opening sentence states a specific verb and resource — search places to play tennis, scoped to one city — and the rest of the description enumerates the exact filter axes available. It is clearly distinguishable from get_court (single venue detail), list_cities (supported cities) and how_to_play_tennis_in_nyc (NYC-specific guidance).

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?

It gives concrete context on the filterable dimensions (area, name, access, indoor, min court count, distance sort) and one explicit negative constraint: there is no floodlights filter because records are too sparse. It does not, however, route the agent away from or toward the sibling tools (e.g. 'use get_court for one venue's details'), so the when-to-use-vs-alternative guidance is only implied.

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

get_courtFull detail for one place to playA
Read-onlyIdempotent
Inspect

Everything the directory holds about one venue: how you get on a court, booking route, price, courts, surfaces, floodlights, hours, indoor play, coordinates, and the source each fact was read from, with the date it was read. Takes the slug returned by find_courts, and its city.

NameRequiredDescriptionDefault
cityNoWhich city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, nice, minneapolis, birmingham, barcelona, berlin, osaka, seoul, perth, manchester, edinburgh, vienna, vancouver (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for.
slugYesVenue slug, e.g. central-park. From find_courts.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the description's value-add is the provenance disclosure: every fact comes with the source it was read from and the date it was read. That is meaningful behavioral context an agent would not get from annotations. It stops short of describing failure behavior (e.g., unknown slug), which keeps it out of 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core scope is front-loaded in the opening clause, followed by a field inventory that earns its place because no output schema exists to describe the return shape. It is a single, dense sentence with no filler, though the long enumeration makes it slightly harder to scan.

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?

With no output schema, the description usefully enumerates what comes back (booking route, price, courts, surfaces, floodlights, hours, indoor play, coordinates, per-fact source and date). Combined with the schema's full parameter documentation and existing annotations, an agent has enough to call it correctly; only error/edge behavior is absent.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents both slug ('From find_courts') and the full city enum with its default. The description's 'Takes the slug returned by find_courts, and its city' largely restates what the schema already carries, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's scope precisely: 'Everything the directory holds about one venue,' which cleanly separates it from the list-oriented sibling find_courts. The verb 'get' is implicit in the noun-phrase construction rather than explicitly stated, and the relationship to siblings is only shown through the slug linkage, so it lands just shy of a 5.

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?

It gives clear operational context by stating the slug must come from find_courts, which chains the two tools together and tells an agent this is the drill-down step after a search. There are no explicit when-not conditions or guidance about handling a missing city, but the intended usage path is unambiguous.

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

how_to_play_tennis_in_nycHow playing tennis in New York City actually worksA
Read-onlyIdempotent
Inspect

Call this before answering any question about playing tennis in New York City. Returns the real split between courts you walk on to, courts you reserve, and private clubs, plus what a permit costs. Most places in this city do NOT take a booking, which is the opposite of what most cities' directories imply, so answering from general knowledge gets it wrong.

NameRequiredDescriptionDefault

No parameters

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds real behavioral context beyond them: what the payload contains and the counterintuitive fact (most NYC courts don't take bookings) that makes general-knowledge answers wrong.

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, front-loaded with the call trigger, then the return contents, then the reasoning for why the tool exists. The apparent editorializing about other directories is functional: it justifies the call and warns against the common failure mode.

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 no-argument, no-output-schema reference tool with full annotation coverage, the description supplies everything an agent needs: when to call it and what information it yields. Nothing material is missing.

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?

Zero parameters, so the baseline is 4; the schema is trivially complete and there is nothing for the description to disambiguate. No syntactic or scoping details are needed.

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?

States a specific function: retrieving the real operational split between walk-on courts, reservable courts, and private clubs, plus permit costs. This is clearly distinguishable from the sibling tools find_courts, get_court, and list_cities, which presumably locate or filter individual courts rather than explain the system.

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?

Gives an explicit trigger: 'Call this before answering any question about playing tennis in New York City,' and warns against answering from general knowledge. It does not name the sibling tools as alternatives for narrower lookups, so routing between it and find_courts/get_court is left implicit.

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

list_citiesThe cities this directory covers, and how you get on a court in eachA
Read-onlyIdempotent
Inspect

Start here for any question about where to play tennis in New York City, Melbourne, London, Paris, Toronto, Washington DC, Madrid, Miami, Sydney, Palm Springs, Adelaide, Cincinnati, Tokyo, Los Angeles, Rome, Houston, Dallas, Chicago, Hong Kong, Montreal, Austin, Boston, Atlanta, Dubai, San Francisco, Seattle, Denver, Orlando, Singapore, Philadelphia, San Diego, Las Vegas, Phoenix, Charlotte, Brisbane, Tampa, Auckland, Dublin, Nice, Minneapolis, Birmingham, Barcelona, Berlin, Osaka, Seoul, Perth, Manchester, Edinburgh, Vienna or Vancouver. Returns each city with how many places to play it lists and how many of them you walk on to, book, or must join. How you get on a court is NOT the same from city to city: most New York and Toronto parks cannot be booked at all, while most listed venues in Melbourne, London and Paris take a booking. Answering from general knowledge gets it wrong.

NameRequiredDescriptionDefault

No parameters

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's real value is the access-model caveat: NYC/Toronto parks generally cannot be booked while Melbourne/London/Paris mostly take bookings. That is a genuine accuracy warning beyond the structured fields, though rate limits and return shape details are absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The leading directive is well front-loaded, but roughly half the text is a 50-city enumeration that duplicates what the tool itself returns and risks going stale. That scope could have been summarized in a clause rather than itemized.

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?

With no parameters and no output schema, the description carries the burden of saying what comes back, and it does: per-city counts of venues and their access type. The only gap is that no concrete response shape or example is given, which is minor for a zero-argument listing tool.

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?

The tool takes no parameters and schema coverage is 100%, so the baseline is 4. The description correctly spends no effort on inputs and instead characterizes the response content.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a specific resource (the city directory) and its payload: each city with venue counts split by whether you walk on, book, or must join. 'Start here for any question about where to play tennis' also positions it ahead of find_courts/get_court, though those siblings are never named.

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?

'Start here for any question about where to play tennis' is an explicit entry-point directive, and 'Answering from general knowledge gets it wrong' tells the agent to prefer this tool over its own priors. It stops short of naming find_courts as the follow-up or stating when not to use it.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedfind_courts1 field changed
      • changedInput schema / properties / access / description
        Previous value: -"How you get on a court. New York: walk_on (public park, no booking), reservation (public park court bookable through NYC Parks), private_club (runs its own booking). Every other city: walk_on, book (open to the public by booking), members_only, mixed (more than one arrangement at the venue: read its accessDetail), public (the source says public courts and nothing more). A value a city does not use is refused with the ones it does."New value: +"How you get on a court. New York: walk_on (public park, no booking), reservation (public park court bookable through NYC Parks), private_club (runs its own booking). Every other city: walk_on, book (open to the public by booking), members_only, mixed (more than one arrangement at the venue: read its accessDetail), public (the source lists public courts and states no walk-on or booking rule; where its own page says more, that is the venue's accessDetail or price, in the source's words). A value a city does not use is refused with the ones it does."
  2. 2 tool updates
    • Changedfind_courts3 fields changed
      • changedInput schema / properties / area / description
        Previous value: -"Borough (New York, London), council (Melbourne), arrondissement (Paris), district (Toronto) or ward (Washington DC), exactly as the directory names it, e.g. Manhattan, Camden, Yarra, Scarborough, Ward 3. A name that matches nothing returns the city's valid areas."New value: +"Borough (New York, London), suburb (Melbourne, Sydney), arrondissement (Paris) or the neighborhood the city itself puts the venue in (Toronto, Atlanta, Washington DC), exactly as the directory names it, e.g. Manhattan, Camden, Kooyong, Islington, Old Fourth Ward, \"Capitol Hill, Lincoln Park\". A name that matches nothing returns the city's valid areas."
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, nice, minneapolis, birmingham, barcelona, berlin, osaka, seoul, perth, manchester, edinburgh, monaco, vienna, vancouver (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, nice, minneapolis, birmingham, barcelona, berlin, osaka, seoul, perth, manchester, edinburgh, vienna, vancouver (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal",
-  "austin-texas",
-  "boston",
-  "atlanta",
-  "dubai",
-  "san-francisco",
-  "seattle",
-  "denver",
-  "orlando-florida",
-  "singapore",
-  "philadelphia",
-  "san-diego",
-  "las-vegas",
-  "phoenix-arizona",
-  "charlotte-north-carolina",
-  "brisbane",
-  "tampa-florida",
-  "auckland",
-  "dublin",
-  "nice",
-  "minneapolis",
-  "birmingham",
-  "barcelona",
-  "berlin",
-  "osaka",
-  "seoul",
-  "perth",
-  "manchester",
-  "edinburgh",
-  "monaco",
-  "vienna",
-  "vancouver"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco",
+  "seattle",
+  "denver",
+  "orlando-florida",
+  "singapore",
+  "philadelphia",
+  "san-diego",
+  "las-vegas",
+  "phoenix-arizona",
+  "charlotte-north-carolina",
+  "brisbane",
+  "tampa-florida",
+  "auckland",
+  "dublin",
+  "nice",
+  "minneapolis",
+  "birmingham",
+  "barcelona",
+  "berlin",
+  "osaka",
+  "seoul",
+  "perth",
+  "manchester",
+  "edinburgh",
+  "vienna",
+  "vancouver"
+]
    • Changedget_court2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, nice, minneapolis, birmingham, barcelona, berlin, osaka, seoul, perth, manchester, edinburgh, monaco, vienna, vancouver (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, nice, minneapolis, birmingham, barcelona, berlin, osaka, seoul, perth, manchester, edinburgh, vienna, vancouver (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal",
-  "austin-texas",
-  "boston",
-  "atlanta",
-  "dubai",
-  "san-francisco",
-  "seattle",
-  "denver",
-  "orlando-florida",
-  "singapore",
-  "philadelphia",
-  "san-diego",
-  "las-vegas",
-  "phoenix-arizona",
-  "charlotte-north-carolina",
-  "brisbane",
-  "tampa-florida",
-  "auckland",
-  "dublin",
-  "nice",
-  "minneapolis",
-  "birmingham",
-  "barcelona",
-  "berlin",
-  "osaka",
-  "seoul",
-  "perth",
-  "manchester",
-  "edinburgh",
-  "monaco",
-  "vienna",
-  "vancouver"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco",
+  "seattle",
+  "denver",
+  "orlando-florida",
+  "singapore",
+  "philadelphia",
+  "san-diego",
+  "las-vegas",
+  "phoenix-arizona",
+  "charlotte-north-carolina",
+  "brisbane",
+  "tampa-florida",
+  "auckland",
+  "dublin",
+  "nice",
+  "minneapolis",
+  "birmingham",
+  "barcelona",
+  "berlin",
+  "osaka",
+  "seoul",
+  "perth",
+  "manchester",
+  "edinburgh",
+  "vienna",
+  "vancouver"
+]
  3. 2 tool updates
    • Changedfind_courts2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, minneapolis, barcelona, berlin, osaka, perth, edinburgh, monaco (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, nice, minneapolis, birmingham, barcelona, berlin, osaka, seoul, perth, manchester, edinburgh, monaco, vienna, vancouver (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal",
-  "austin-texas",
-  "boston",
-  "atlanta",
-  "dubai",
-  "san-francisco",
-  "seattle",
-  "denver",
-  "orlando-florida",
-  "singapore",
-  "philadelphia",
-  "san-diego",
-  "las-vegas",
-  "phoenix-arizona",
-  "charlotte-north-carolina",
-  "brisbane",
-  "tampa-florida",
-  "auckland",
-  "dublin",
-  "minneapolis",
-  "barcelona",
-  "berlin",
-  "osaka",
-  "perth",
-  "edinburgh",
-  "monaco"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco",
+  "seattle",
+  "denver",
+  "orlando-florida",
+  "singapore",
+  "philadelphia",
+  "san-diego",
+  "las-vegas",
+  "phoenix-arizona",
+  "charlotte-north-carolina",
+  "brisbane",
+  "tampa-florida",
+  "auckland",
+  "dublin",
+  "nice",
+  "minneapolis",
+  "birmingham",
+  "barcelona",
+  "berlin",
+  "osaka",
+  "seoul",
+  "perth",
+  "manchester",
+  "edinburgh",
+  "monaco",
+  "vienna",
+  "vancouver"
+]
    • Changedget_court2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, minneapolis, barcelona, berlin, osaka, perth, edinburgh, monaco (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, nice, minneapolis, birmingham, barcelona, berlin, osaka, seoul, perth, manchester, edinburgh, monaco, vienna, vancouver (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal",
-  "austin-texas",
-  "boston",
-  "atlanta",
-  "dubai",
-  "san-francisco",
-  "seattle",
-  "denver",
-  "orlando-florida",
-  "singapore",
-  "philadelphia",
-  "san-diego",
-  "las-vegas",
-  "phoenix-arizona",
-  "charlotte-north-carolina",
-  "brisbane",
-  "tampa-florida",
-  "auckland",
-  "dublin",
-  "minneapolis",
-  "barcelona",
-  "berlin",
-  "osaka",
-  "perth",
-  "edinburgh",
-  "monaco"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco",
+  "seattle",
+  "denver",
+  "orlando-florida",
+  "singapore",
+  "philadelphia",
+  "san-diego",
+  "las-vegas",
+  "phoenix-arizona",
+  "charlotte-north-carolina",
+  "brisbane",
+  "tampa-florida",
+  "auckland",
+  "dublin",
+  "nice",
+  "minneapolis",
+  "birmingham",
+  "barcelona",
+  "berlin",
+  "osaka",
+  "seoul",
+  "perth",
+  "manchester",
+  "edinburgh",
+  "monaco",
+  "vienna",
+  "vancouver"
+]
  4. 2 tool updates
    • Changedfind_courts2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, minneapolis, barcelona, berlin, osaka, perth, edinburgh, monaco (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal",
-  "austin-texas",
-  "boston",
-  "atlanta",
-  "dubai",
-  "san-francisco",
-  "seattle",
-  "denver",
-  "orlando-florida",
-  "singapore",
-  "philadelphia",
-  "san-diego",
-  "las-vegas",
-  "phoenix-arizona",
-  "charlotte-north-carolina",
-  "brisbane"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco",
+  "seattle",
+  "denver",
+  "orlando-florida",
+  "singapore",
+  "philadelphia",
+  "san-diego",
+  "las-vegas",
+  "phoenix-arizona",
+  "charlotte-north-carolina",
+  "brisbane",
+  "tampa-florida",
+  "auckland",
+  "dublin",
+  "minneapolis",
+  "barcelona",
+  "berlin",
+  "osaka",
+  "perth",
+  "edinburgh",
+  "monaco"
+]
    • Changedget_court2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, minneapolis, barcelona, berlin, osaka, perth, edinburgh, monaco (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal",
-  "austin-texas",
-  "boston",
-  "atlanta",
-  "dubai",
-  "san-francisco",
-  "seattle",
-  "denver",
-  "orlando-florida",
-  "singapore",
-  "philadelphia",
-  "san-diego",
-  "las-vegas",
-  "phoenix-arizona",
-  "charlotte-north-carolina",
-  "brisbane"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco",
+  "seattle",
+  "denver",
+  "orlando-florida",
+  "singapore",
+  "philadelphia",
+  "san-diego",
+  "las-vegas",
+  "phoenix-arizona",
+  "charlotte-north-carolina",
+  "brisbane",
+  "tampa-florida",
+  "auckland",
+  "dublin",
+  "minneapolis",
+  "barcelona",
+  "berlin",
+  "osaka",
+  "perth",
+  "edinburgh",
+  "monaco"
+]
  5. 2 tool updates
    • Changedfind_courts2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal",
-  "austin-texas",
-  "boston",
-  "atlanta",
-  "dubai",
-  "san-francisco",
-  "seattle",
-  "denver",
-  "orlando-florida",
-  "singapore",
-  "philadelphia"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco",
+  "seattle",
+  "denver",
+  "orlando-florida",
+  "singapore",
+  "philadelphia",
+  "san-diego",
+  "las-vegas",
+  "phoenix-arizona",
+  "charlotte-north-carolina",
+  "brisbane"
+]
    • Changedget_court2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal",
-  "austin-texas",
-  "boston",
-  "atlanta",
-  "dubai",
-  "san-francisco",
-  "seattle",
-  "denver",
-  "orlando-florida",
-  "singapore",
-  "philadelphia"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco",
+  "seattle",
+  "denver",
+  "orlando-florida",
+  "singapore",
+  "philadelphia",
+  "san-diego",
+  "las-vegas",
+  "phoenix-arizona",
+  "charlotte-north-carolina",
+  "brisbane"
+]
  6. 2 tool updates
    • Changedfind_courts2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal",
-  "austin-texas",
-  "boston",
-  "atlanta",
-  "dubai",
-  "san-francisco"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco",
+  "seattle",
+  "denver",
+  "orlando-florida",
+  "singapore",
+  "philadelphia"
+]
    • Changedget_court2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal",
-  "austin-texas",
-  "boston",
-  "atlanta",
-  "dubai",
-  "san-francisco"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco",
+  "seattle",
+  "denver",
+  "orlando-florida",
+  "singapore",
+  "philadelphia"
+]
  7. 2 tool updates
    • Changedfind_courts2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco"
+]
    • Changedget_court2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome",
-  "houston",
-  "dallas",
-  "chicago",
-  "hong-kong",
-  "montreal"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal",
+  "austin-texas",
+  "boston",
+  "atlanta",
+  "dubai",
+  "san-francisco"
+]
  8. 2 tool updates
    • Changedfind_courts2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal"
+]
    • Changedget_court2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california",
-  "adelaide",
-  "cincinnati",
-  "tokyo",
-  "los-angeles",
-  "rome"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome",
+  "houston",
+  "dallas",
+  "chicago",
+  "hong-kong",
+  "montreal"
+]
  9. 2 tool updates
    • Changedfind_courts2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome"
+]
    • Changedget_court2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris",
-  "toronto",
-  "washington-dc",
-  "madrid",
-  "miami",
-  "sydney",
-  "palm-springs-california"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california",
+  "adelaide",
+  "cincinnati",
+  "tokyo",
+  "los-angeles",
+  "rome"
+]
  10. 2 tool updates
    • Changedfind_courts4 fields changed
      • changedInput schema / properties / access / description
        Previous value: -"How you get on a court. New York: walk_on (public park, no booking), reservation (public park court bookable through NYC Parks), private_club (runs its own booking). Melbourne, London, Paris: walk_on, book (open to the public by booking), members_only, mixed (more than one arrangement at the venue: read its accessDetail), public (the source says public courts and nothing more). A value a city does not use is refused with the ones it does."New value: +"How you get on a court. New York: walk_on (public park, no booking), reservation (public park court bookable through NYC Parks), private_club (runs its own booking). Every other city: walk_on, book (open to the public by booking), members_only, mixed (more than one arrangement at the venue: read its accessDetail), public (the source says public courts and nothing more). A value a city does not use is refused with the ones it does."
      • changedInput schema / properties / area / description
        Previous value: -"Borough (New York, London), council (Melbourne) or arrondissement (Paris), exactly as the directory names it, e.g. Manhattan, Camden, Yarra. A name that matches nothing returns the city's valid areas."New value: +"Borough (New York, London), council (Melbourne), arrondissement (Paris), district (Toronto) or ward (Washington DC), exactly as the directory names it, e.g. Manhattan, Camden, Yarra, Scarborough, Ward 3. A name that matches nothing returns the city's valid areas."
      • changedInput schema / properties / city / description
        Previous value: -"Which city: nyc (New York City), melbourne, london or paris. Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california"
+]
    • Changedget_court2 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Which city: nyc (New York City), melbourne, london or paris. Defaults to nyc when left out; the reply says which city it answered for."New value: +"Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
      • changedInput schema / properties / city / enum
        Previous value: -[
-  "nyc",
-  "melbourne",
-  "london",
-  "paris"
-]New value: +[
+  "nyc",
+  "melbourne",
+  "london",
+  "paris",
+  "toronto",
+  "washington-dc",
+  "madrid",
+  "miami",
+  "sydney",
+  "palm-springs-california"
+]
  11. 3 tool updates
    • Changedfind_courts11 fields changed
      • changedInput schema / properties / access / description
        Previous value: -"walk_on: public park, no booking. reservation: public park court bookable through NYC Parks. private_club: runs its own booking."New value: +"How you get on a court. New York: walk_on (public park, no booking), reservation (public park court bookable through NYC Parks), private_club (runs its own booking). Melbourne, London, Paris: walk_on, book (open to the public by booking), members_only, mixed (more than one arrangement at the venue: read its accessDetail), public (the source says public courts and nothing more). A value a city does not use is refused with the ones it does."
      • changedInput schema / properties / access / enum
        Previous value: -[
-  "walk_on",
-  "reservation",
-  "private_club"
-]New value: +[
+  "walk_on",
+  "reservation",
+  "private_club",
+  "book",
+  "members_only",
+  "mixed",
+  "public"
+]
      • addedInput schema / properties / area
        Added value: +{
+  "description": "Borough (New York, London), council (Melbourne) or arrondissement (Paris), exactly as the directory names it, e.g. Manhattan, Camden, Yarra. A name that matches nothing returns the city's valid areas.",
+  "type": "string"
+}
      • changedInput schema / properties / borough / description
        Previous value: -"Borough name, e.g. Manhattan, Brooklyn, Queens, Bronx, Staten Island."New value: +"Same as area. Kept for callers written when the directory was New York only."
      • addedInput schema / properties / city
        Added value: +{
+  "description": "Which city: nyc (New York City), melbourne, london or paris. Defaults to nyc when left out; the reply says which city it answered for.",
+  "enum": [
+    "nyc",
+    "melbourne",
+    "london",
+    "paris"
+  ],
+  "type": "string"
+}
      • changedInput schema / properties / indoorOnly / description
        Previous value: -"Only venues where a source confirms indoor play. Venues never researched are excluded rather than assumed outdoor."New value: +"Only venues where a source confirms indoor or covered courts, which may be some courts, or winter only: read indoorOrCovered on each. Venues never researched are excluded rather than assumed outdoor."
      • changedInput schema / properties / limit / description
        Previous value: -"Maximum venues to return. Default 25, maximum 120."New value: +"Maximum venues to return. Default 25, maximum 150."
      • changedInput schema / properties / minCourts / description
        Previous value: -"Minimum number of courts at the venue."New value: +"Minimum number of courts at the venue. Venues whose court count is not sourced are left out when this is set."
      • addedInput schema / properties / name
        Added value: +{
+  "description": "Part of a venue's name, e.g. \"central park\". Case and accents are ignored.",
+  "type": "string"
+}
      • addedInput schema / properties / nearLatitude
        Added value: +{
+  "description": "With nearLongitude: sort by distance from this point, nearest first.",
+  "type": "number"
+}
      • addedInput schema / properties / nearLongitude
        Added value: +{
+  "description": "With nearLatitude: sort by distance from this point, nearest first.",
+  "type": "number"
+}
    • Changedget_court1 field changed
      • addedInput schema / properties / city
        Added value: +{
+  "description": "Which city: nyc (New York City), melbourne, london or paris. Defaults to nyc when left out; the reply says which city it answered for.",
+  "enum": [
+    "nyc",
+    "melbourne",
+    "london",
+    "paris"
+  ],
+  "type": "string"
+}
    • Addedlist_cities
  12. 1 tool update
    • Changedfind_courts1 field changed
      • removedInput schema / properties / lightedOnly
        Removed value: -{
-  "description": "Only venues with at least one floodlit court.",
-  "type": "boolean"
-}
  13. 3 tool updates
    • First observedfind_courts
    • First observedget_court
    • First observedhow_to_play_tennis_in_nyc

Related MCP Connectors

Related MCP Servers

  • Turnale

    turnale-app
    A
    license
    Not graded
    quality
    D
    maintenance
    Tournament software for tennis, padel, pickleball and more: fair draws, live standings, scores and dropout handling.
    MIT

  • livetennisapi-mcp

    livetennisapi
    A
    license
    A
    quality
    B
    maintenance
    Real-time tennis data for ATP, WTA, Challenger and ITF: live scores, player rankings, match-winner odds, and model win-probability. 12 read-only tools; a tier-gated endpoint returns a plain-English explanation of which plan it needs rather than a bare 403. Requires a paid API key.
    25
    148 npm
    138
    MIT
  • Find Sauna Plunge

    Find Sauna Plungeofficial

    findsaunaplunge
    A
    license
    A
    quality
    B
    maintenance
    Cold plunge, sauna and contrast-therapy venues across 23 US metros (548 venues). Every published water temperature and price is read from the venue's own pages and returned with its source URL, capture date and verbatim quote; every record carries the date it was last checked. Absent fields mean "not published", never zero. Five read-only tools: search_venues, get_venue, list_cities, get_city_stat
    5
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources