Skip to main content
Glama

Search occupancy certificates

search_certificates
Read-onlyIdempotent

Search certificates of occupancy or completion. Defaults exclude renewals; co_date_basis states what each date means. Completion certificates do not establish occupancy, and pending applications are not issued certificates. Coverage varies by source and place; an empty result does not establish that no record exists. Up to 25 results per call. total_capped marks a lower bound; total_unknown means the total is unknown. Pagination guidance is in _notes.

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": "search_certificates"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lngNo
cityNoCity name (matches the address city or the issuing jurisdiction)
kindNo'occupancy' (default), 'completion' (certificates of completion: close-outs of work that creates no occupancy, e.g. roofs, pools), or 'all'occupancy
pageNoPage number, 1-based (default 1)
startNoInstead of page: 1-based position of the first result to return, e.g. start=24 continues after result 23 (as named in `_notes`)
stateNo2-letter state code
parcelNoParcel / APN / folio / BBL (formatting ignored)
addressNoStreet address, partial, case-insensitive
co_typeNo'change' = re-issued for an existing building's new owner, use or occupant load; 'revision' = a revised certificate. Neither certifies new units: their dwelling units are in units_existing, so min_units counts newly certified units.
per_pageNoResults per page (default 25, max 25)
renewalsNoTemporary-certificate RENEWALS (NYC re-issues a TCO every 90 days). Default 'exclude': finals and first-time TCOs only.exclude
zip_codeNo5-digit ZIP
co_numberNo
min_unitsNoNewly certified dwelling units on or above (units_existing is not counted)
issued_afterNoCO date on or after (undated certificates never match)
radius_milesNoRadius in miles around lat/lng (default 1)
issued_beforeNoCO date on or before
permit_numberNoThe building permit the certificate was issued on
jurisdiction_idNoA jurisdiction id from /v1/jurisdictions
occupancy_classNoBuilding-code occupancy group as published, e.g. R-3, B
certificate_statusNoDefault: issued + expired (both were issued). 'pending' = CO applications not yet issued.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context beyond them: 25-result cap, coverage varying by source and place, empty results not proving absence, and the meaning of total_capped/total_unknown. It does not describe the result object shape, but the caveats about totals and coverage are exactly the kind of context an agent needs.

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?

Front-loaded with the core purpose, then a compact sequence of caveats, each of which carries information an agent would otherwise get wrong. Slightly dense and caveat-heavy, but no sentence is 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 22 optional parameters and no output schema, the description does the necessary work of explaining result-count semantics (total_capped, total_unknown) and pointing to _notes for pagination. It stops short of describing the returned certificate fields, which is the main remaining gap.

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 86%, so the schema already documents nearly every parameter, including the co_type and renewals enums. The description adds only marginal meaning (renewals default behavior, co_date_basis explaining date fields), so the baseline 3 applies.

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?

States a specific verb and resource ('Search certificates of occupancy or completion') and immediately disambiguates the two record kinds, which is the main confusion risk. It does not explicitly contrast with the get_certificate sibling, but the search-vs-fetch distinction is clear from the name and scope.

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?

Gives useful interpretive guidance (defaults exclude renewals, completion certificates do not establish occupancy, pending applications are not issued certificates) but never states when to use this tool versus get_certificate or the other search_* tools. Usage context is implied rather than prescribed.

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