nyrezone-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_lotA | Look up one NYC tax lot by street address OR 10-digit BBL (borough-block-lot). Returns zoning district(s), built vs. allowed FAR, lot and building area, an estimated unused floor area, year built and land use, from MapPLUTO via NYRezone. Provide exactly one of address or bbl. Addresses must start with a house number and should include the borough; an ambiguous or unknown address returns an error instead of a guess. Owner and assessment data are never returned. |
| get_zoning_districtA | Get the rules NYRezone publishes for one NYC zoning district code (e.g. R6A, C4-2, M1-2/R6A): max FAR, base and maximum height, bonuses, citywide lot counts and average built FAR. Height/setback detail is only what NYRezone publishes for that district. An unknown code returns the list of valid codes. |
| list_zoning_districtsA | List the NYC zoning district codes NYRezone documents, each with a one-line summary (its district family description). Optionally filter by family, e.g. R6 or C4. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct object and action: lookup_lot retrieves a specific lot, get_zoning_district returns rules for one district code, and list_zoning_districts enumerates available codes. There is no overlap that would cause an agent to misselect.
All three names follow a verb_noun snake_case pattern (lookup_lot, get_zoning_district, list_zoning_districts). The verbs (lookup/get/list) are distinct and clearly map to their operations.
Three tools is lean but well-scoped for a read-only zoning/lot lookup service. Each tool earns its place, though it sits near the thin end of the acceptable range.
The core lookup lifecycle (resolve a lot, inspect a district's rules, enumerate districts) is covered with no dead ends. Minor gaps exist, such as no way to search lots by district or perform batch/area queries, but the primary use cases are handled.