nyc-311-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NYC_311_API_KEY | Yes | NYC 311 Public API subscription key. Obtain from https://api-portal.nyc.gov/ |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_calendarA | Get Alternate Side Parking, Garbage & Recycling, and Schools status for a date or date range (max 90 days). Dates are interpreted in America/New_York (Eastern Time); if no date is given, defaults to today in New York. |
| get_statusA | Get the current city status for an emergency or weather condition: Code Blue (cold weather), Fire Hydrant, OEM emergency notifications, Snow on Sidewalk, or Snow on Street. |
| get_service_requestA | Look up one 311 service request by its number (format 311-XXXXXXXX). Returns agency, problem type, status, timestamp, and address. |
| get_service_request_listB | Bulk look up multiple 311 service requests by their numbers in a single call. |
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 4 tools
Each tool targets a distinct function: calendar info, single request lookup, batch request lookup, and emergency/weather status. No overlap in purpose.
All tool names follow the consistent pattern 'get_<noun>' with snake_case, making them predictable and easy to understand.
Four tools is a reasonable size for a focused read-only service, though it could be expanded with additional lookup or search tools without becoming unwieldy.
The server covers basic lookups and calendar/status, but lacks search by location, category, or the ability to create requests, leaving notable gaps for a 311 service.