Skip to main content
Glama

nyc-tennis-courts

by tennis.courts
OverviewDiscussionsAdmin

Find places to play tennis in New York City

find_courts

Search the directory of places to play tennis in New York City. Filter by borough, by how you get on a court (walk_on, reservation, private_club), by indoor play, by floodlights, or by minimum court count. Returns each venue with its page URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum venues to return. Default 25, maximum 120.
accessNowalk_on: public park, no booking. reservation: public park court bookable through NYC Parks. private_club: runs its own booking.
boroughNoBorough name, e.g. Manhattan, Brooklyn, Queens, Bronx, Staten Island.
minCourtsNoMinimum number of courts at the venue.
indoorOnlyNoOnly venues where a source confirms indoor play. Venues never researched are excluded rather than assumed outdoor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / lightedOnly
      Removed value: -{
-  "description": "Only venues with at least one floodlit court.",
-  "type": "boolean"
-}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses a read-only search behavior, the filter semantics, and the return value (venues with page URLs). The note about indoorOnly excluding unresearched venues rather than assuming they are outdoor adds valuable behavioral detail beyond the schema.

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 deliver the full purpose, filter capabilities, and return behavior with no filler. The main action is front-loaded, and the conservative indoorOnly behavior earns its place.

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?

The description explains the key filters and states that each returned venue includes its page URL, which is enough for an agent to invoke the tool and continue with get_court. It does not enumerate all return fields, but the absence of an output schema is mitigated by the explicit URL mention.

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?

The input schema already covers all 5 parameters with 100% description coverage, so the baseline of 3 applies. The description lists some filter categories, but it does not add meaningful semantic detail beyond what the schema already provides for each parameter.

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 clearly states a specific verb ('Search') and resource ('the directory of places to play tennis in New York City'), and lists concrete filter dimensions. It does not explicitly distinguish itself from siblings like get_court, but the directory-search framing is distinct enough to be unambiguous.

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

Usage Guidelines3/5

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

The description implies the tool is for finding a list of tennis venues while providing no explicit guidance about when to prefer it over get_court or how_to_play_tennis_in_nyc. It gives clear context for its own use but no exclusions or alternative routing.

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

All nyc-tennis-courts 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.

Resources