nyc-rent-check
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOCRATA_APP_TOKEN | No | A free Socrata app token for higher rate limits (optional). |
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_buildingB | Resolve an NYC address to its official BBL (tax lot) and BIN (building ID) via NYC Planning GeoSearch. |
| building_reportA | Full public-records report for an NYC residential building: HPD violations (open and closed, by class A/B/C), annual bed bug filings, 311 heat/hot water and noise complaints from the last 24 months, and DOB complaints. |
| red_flagsA | Plain-English verdict on an NYC building with the top 3 concerns from city records. Use this for a quick 'should I worry?' answer. |
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 has a clearly distinct role: lookup_building resolves an address, building_report returns full public records, and red_flags provides a quick top-concerns verdict. The descriptions explicitly frame red_flags as a summary, so overlap with the full report is unlikely to cause misselection.
All names use snake_case, which is consistent casing, but the grammatical pattern is mixed: lookup_building is verb_noun, while building_report and red_flags are noun phrases. The names remain readable but do not follow one predictable convention.
Three tools is on the lean side but well-scoped for a focused NYC building-check service, with each tool serving a clear, non-redundant purpose. It avoids both bloat and excessive fragmentation.
The set covers the core workflow: resolve an address, pull the full public-records report, and get a plain-English red-flag summary. Minor gaps exist, such as direct rent-stabilization or eviction-record checks, but the main rental-risk questions are addressed.