Skip to main content
Glama
nyc-311-mcp

nyc-311-mcp

address_history

Retrieves every NYC 311 service request for a given address, newest first, with status, days open or closed, resolution text, and issue-type counts; supports date, status, and borough filters.

Instructions

Every request at one address, newest first, with its status, days to close or days open, and the agency's resolution text, plus counts by problem. The address is converted to the City's spelling as in find_district. With no dates, covers every request since 2020. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "address_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to list (default 50).
offsetNoRows to skip (default 0); for the next page, next_page.offset.
statusNo'not_closed' = any status but Closed.
addressYesStreet address, e.g. '1000 5th Ave'.
boroughNoNeeded when the same address exists in several boroughs.
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).
data_as_ofNoFor the next page, next_page.data_as_of; a page from a newer build is refused.
fiscal_yearNoNYC fiscal year: 2027 or 'FY2027' = 2026-07-01 to 2027-06-30.
community_districtNoOptional: the district (BoardStat id) to use when the address straddles a line. Default: the one with the most requests there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.9/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 behavioral burden and does well: it discloses ordering, returned fields, default date coverage, source provenance, that it is not an official City report, and key semantic caveats like counts being reports and 'closed' not meaning 'fixed'. It does not discuss permissions, rate limits, or error behavior, but for a public read-only data tool this is substantial context.

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?

The description is front-loaded with the core return content and then layers on normalization, default date range, provenance, and semantic caveats. Every sentence adds useful context without repetition or filler.

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?

For a 12-parameter tool with no output schema and no annotations, the description is nearly complete: it explains the record shape, default date coverage, address normalization, and important caveats. Minor gaps remain around output pagination structure and error cases, but the schema covers most parameter-level detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema by explaining that the address is normalized to the City's spelling as in find_district and that omitting date parameters defaults to all requests since 2020.

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 states a specific resource and scope: every 311 request at one address, newest first, with status, days to close/open, resolution text, and problem counts. It is clearly distinguishable from a generic request search, though it does not directly contrast itself with sibling tools like find_requests.

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 implied by the address-centric scope and the note that no dates means every request since 2020. However, there is no explicit guidance on when to choose this over find_requests, get_service_request, or top_addresses, and no when-not-to-use section.

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