Skip to main content
Glama

search_nyc_violations

Search NYC Department of Buildings violation records using address, BIN, or block+lot. Retrieve DOB, Safety, and ECB violations with penalty amounts. Enable summary mode for aggregate statistics.

Instructions

Search NYC Department of Buildings violation records by address, BIN, or block+lot. Covers DOB Violations, Safety Violations, and ECB Violations (with penalty amounts). Use summary=true for aggregate stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
house_numberNoHouse number (e.g. "350"). Use with street.
streetNoStreet name (e.g. "BROADWAY"). Use with house_number.
binNoNYC BIN (Building Identification Number)
blockNoTax block number (use with lot)
lotNoTax lot number (use with block)
boroughNoBorough: manhattan, bronx, brooklyn, queens, or "staten island"
summaryNoSet true for aggregate stats instead of individual violations
limitNoMax results (ignored when summary=true)
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It lacks details on authentication, rate limits, error behavior, or any side effects. Only states what it covers, not how it behaves.

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?

Two concise sentences, front-loaded with action and scope. Every sentence adds value without redundancy.

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

Completeness2/5

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

Given 8 parameters, no output schema, and no annotations, the description is too minimal. It omits return format, error handling, and how the three violation types appear in results. Needs more detail for completeness.

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%, so baseline is 3. Description adds grouping (address, BIN, block+lot) and clarifies summary+limit interaction, but these are minor additions beyond what schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it searches NYC building violation records, specifies types (DOB, Safety, ECB) and indicates scope (by address, BIN, block+lot). Distinct from sibling tools which cover other domains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes when to use (for NYC violation records) and gives example filter combinations. No explicit mention of when not to use, but given unique domain, this is acceptable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lulzasaur9192/marketplace-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server