Skip to main content
Glama

Woodpecker: NYC HPD registration lookup

Look up a NYC building by address

lookup_nyc_building
Read-onlyIdempotent

Finds a New York City residential building in HPD's records by borough, house number and street, and returns its registration status (valid, expired or missing), open filing violations, apartment count and Woodpecker's yearly price for it. Use when the user gives an address.

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": {
      "borough": "<borough>",
      "house_number": "<house_number>",
      "street": "<street>"
    },
    "name": "lookup_nyc_building"
  }
}

Input Schema

NameRequiredDescriptionDefault
streetYesStreet name, like East 56 Street or Bushwick Avenue
boroughYesBrooklyn, Queens, Bronx, Manhattan or Staten Island
house_numberYesHouse number as on the building, like 787 or 100-02

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: the underlying data source (HPD records), the three possible registration statuses (valid, expired, missing), and the fact that a Woodpecker yearly price is attached. It still doesn't state what happens when the address isn't found at all.

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?

Two sentences, front-loaded with the verb and scope, then the return payload. The enumerated return fields are dense but each carries information an agent needs to decide whether to call it; there is no 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?

With no output schema, the description correctly takes on the job of describing returns, and it does so specifically. Three required params are fully documented by the schema. The remaining gap is a note on the no-match case and a contrast with the similarly named get_nyc_building.

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% and the schema already supplies format examples like 'East 56 Street' and '100-02'. The description only restates the three keys as 'borough, house number and street', adding no syntax, normalization, or edge-case meaning beyond the schema.

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 uses a specific verb and resource ('Finds a New York City residential building in HPD's records') and enumerates exactly what comes back: registration status, open filing violations, apartment count and Woodpecker yearly price. It is clear on its own, but it never differentiates itself from the sibling get_nyc_building, whose name suggests overlapping behavior.

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?

'Use when the user gives an address' gives a concrete trigger condition, which is more than nothing. However, it offers no exclusions or alternatives — nothing tells the agent when to prefer get_nyc_building, or to use open_hpd_filing_violations_by_borough for portfolio-level violation browsing.

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.