Skip to main content
Glama

property-violations-history

Property Code-Violation & Lien History (Open-Data Cities) — Before buying, leasing or insuring a US property, reads the city's own open-data code-enforcement records for one address (or a NYC BBL/BIN) and returns normalized violations with date opened, category, description, open/closed status, source severity class and record URL; deterministic counts by status, category and year; days since the latest violation; the longest repeat-citation streak (citati

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": "property-violations-history"
  }
}

Input Schema

NameRequiredDescriptionDefault
bblNoNYC borough-block-lot, 10 digits.
binNoNYC building identification number, 7 digits.
zipNoZIP code (informational; not used to widen a match).
cityNoCity, when not inside address. For NYC a borough name (Brooklyn, Queens, ...) narrows the match.
stateNoTwo-letter state, when not inside address.
addressNoUS street address with city and state, e.g. '447 21st Ave, San Francisco, CA 94121'. Give exactly one of address, bbl or bin.
lookback_yearsNoYears of history to read (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 load and does substantial work: it discloses the data source (municipal open data), the geographic constraint (US cities, NYC identifier support), and the shape of the return (normalized records plus deterministic counts, days since latest violation, repeat-citation streak). It omits permission/auth requirements, rate limits, and what happens when a city has no open-data program, which matters for a read against a municipal API.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The essential scope is front-loaded correctly, which is a strength. But the body is a single sprawling run-on sentence chained with em-dashes and semicolons, and the text terminates mid-word ('(citati'), leaving a promised output field dangling.

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 seven-parameter tool with no output schema and no annotations, the description must do the explaining, and it largely does by enumerating returned fields and derived statistics. The truncated tail and the absence of any zero-results or multi-city coverage behavior leave real gaps an agent would want filled before calling.

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 description coverage is 100%, so all seven parameters are already documented, including the mutually exclusive 'give exactly one of address, bbl or bin' rule and the lookback default. The description only restates the address-vs-BBL/BIN choice and adds no formats, constraints, or precedence rules beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource: reads the city's own open-data code-enforcement records for one address or a NYC BBL/BIN, and enumerates the returned data (violations with date opened, category, status, severity, URL) plus derived metrics. The domain is unmistakable and an agent can distinguish this from a generic 'property-risk' sibling without opening the schema.

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?

The opening clause 'Before buying, leasing or insuring a US property' gives a clear triggering context, which is more than most definitions offer. However, it names no alternatives and states no exclusions, so there is no explicit when-not guidance or routing to a sibling tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources