Skip to main content
Glama
nyc-311-mcp

nyc-311-mcp

top_addresses

Rank addresses in a NYC district by 311 request count for a date range, with optional filters for problem type or descriptor to identify repeat-report locations.

Instructions

The addresses in a district with the most requests for a period, optionally for given problems or descriptions. Addresses are as the City spelled them. From BoardStat (BetaNYC, NYC Open Data, 2020 on); not an official City report. 311 counts are reports, not problems; 'closed' is not 'fixed'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "top_addresses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to list (default 15).
agencyNoAgency code as 311 writes it, e.g. 'NYPD'.
statusNo'not_closed' = any status but Closed.
to_dateNoEnd, YYYY-MM-DD, inclusive.
problemsNoBoardStat problem names, e.g. ['HEAT/HOT WATER']; any case.
from_dateNoStart, YYYY-MM-DD, inclusive.
last_daysNoThe last N days of data, ending on the newest request's day (not today).
fiscal_yearNoNYC fiscal year: 2027 or 'FY2027' = 2026-07-01 to 2027-06-30.
descriptionsNo311 descriptors, e.g. ['Blocked Bike Lane']; a missing one is '(none)'.
council_districtNoCouncil district, 1 to 51. Not with community_district.
community_districtNo306, BK06 or 'Brooklyn 6' (all forms: server instructions). Not with council_district.
exclude_descriptionsNoLeave out these descriptions instead of keeping only them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it adds real value: the read-only/derived nature is evident, addresses appear exactly as the City spelled them (relevant for matching), results come from BoardStat/BetaNYC rather than an official City source, and two interpretive caveats ('counts are reports, not problems'; 'closed is not fixed') prevent misreading counts. It stops short of stating the sort order or the per-row shape, which would complete the behavioral picture.

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 purpose is front-loaded in the first sentence and the remaining sentences are short, distinct caveats that each add information. No filler or repetition, though the provenance and caveat sentences could be tightened slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter tool with no annotations and no output schema, the definition does not say what a returned row looks like (address plus count?), whether results are ordered descending by count, or what happens when no district filter is supplied. The data-provenance caveats are strong, but key invocation-shaping details are left to inference.

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 coverage is 100%, including enum and constraint notes, so the baseline is 3. The description only echoes that problems/descriptions act as optional filters and that results are scoped to a district; it adds no syntax, precedence, or interaction detail (e.g., how last_days, from_date/to_date, and fiscal_year combine) beyond what the schema already documents.

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 first sentence names a specific resource (addresses) and a specific ranking criterion (most 311 requests in a district for a period), with optional problem/description filters. It implicitly separates itself from top_problems by returning addresses rather than problem categories, though it never names a sibling explicitly.

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?

Usage is only implied: 'most requests for a period, optionally for given problems or descriptions' suggests the question this answers, but there is no when-to-use/when-not guidance and no pointer to alternatives such as top_problems, find_requests, or address_history. It also never says that the district scope is effectively mandatory, even though the schema marks no parameter as required.

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